Bug #15479 | Unable to connect to MS SQL Instance | ||
---|---|---|---|
Submitted: | 5 Dec 2005 9:48 | Modified: | 14 Jun 2006 13:15 |
Reporter: | Rachael Russell | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Migration Toolkit | Severity: | S1 (Critical) |
Version: | 1.0.20.rc1 | OS: | Windows (Windows XP) |
Assigned to: | Michael G. Zinner | CPU Architecture: | Any |
[5 Dec 2005 9:48]
Rachael Russell
[5 Dec 2005 9:56]
Valeriy Kravchuk
Thank you for a problem report. Are you able to connect to that MS SQL server with the same hostname, database name, user name etc from any MS SQL tool or using ODBC? Please, check.
[5 Dec 2005 10:04]
Rachael Russell
Yep, i use this Database server all the time - it's running locally on my PC and I can connect with ODBC and other client tools/software also. Here's the ODBC setup - test connections succeed OK. Default TCP/IP port is 1120: Microsoft SQL Server ODBC Driver Version 03.85.1117 Data Source Name: mrInterviewUser Data Source Description: Server: lddtestxp\spss_dimensions Database: (Default) Language: (Default) Translate Character Data: Yes Log Long Running Queries: No Log Driver Statistics: No Use Integrated Security: No Use Regional Settings: No Prepared Statements Option: Drop temporary procedures on disconnect Use Failover Server: No Use ANSI Quoted Identifiers: Yes Use ANSI Null, Paddings and Warnings: Yes Data Encryption: No
[14 Jun 2006 13:15]
Michael G. Zinner
You need to connect via TCP/IP port, not via instance name. The default port number is 1433. You have to enable TCP/IP networking in the MS SQL server if it is not enabled. You can also specify more advanced options by pressing [Advanced] and enter a JDBC connection string directly. Please refere to http://jtds.sourceforge.net/ for more information.
[15 Apr 2010 4:10]
Eduardo Cortes
Wow... Thanks... Now I can sleep... :-)