MySQL Bugs: #18757: MT does not work with Windows authentication mode for MS SQL Server

Bug #18757	MT does not work with Windows authentication mode for MS SQL Server
Submitted:	3 Apr 2006 20:12	Modified:	29 Jun 2006 16:46
Reporter:	Michael Flanagan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S3 (Non-critical)
Version:	1.0.25	OS:	Windows (XP SP2)
Assigned to:	Michael G. Zinner	CPU Architecture:	Any

Description:
I'm unable to migrate my MS SQL unless I add a valid username/password to the MS SQL server, and also enable 'mixed mode authentication' (SQL Server & Windows). I would rather not have SQL Server authentication, so my SQL Server instance had no usernames defined. But the MT won't allow that. I tried a blank username, but of course that didn't work.

The simple workaround is to change authentication on the server to mixed mode, and then add a username/password to the database, then do the migration, then reverse the username fol-de-rol.

How to repeat:
Change the server's security setting to 'Windows only' and try to migrate. The error should be that you cannot connect to the MS SQL server (error might say something about lack of a trusted connection).

Suggested fix:
Allow null values in the username and password ui fields for MS SQL. If those fields are determined to be empty, then don't pass them through JDBC. (Does JDBC allow this?)

Or, allow the user to specify an ODBC connection name, and put all the info in there. (Again, does JDBC work with MS Data Sources (ODBC)?)

Thank you for the bug. I suggest you to change the synopsis to MT not
works with Windows authentication mode for MS SQL Server.

Updated synopsis to "MT does not work with Windows authentication mode for MS SQL Server."

I have added a new field "Domain:" that allows you to specify a domain name. If it is set, NTLM authentication is used. This feature will be in the next release.

If you need more detail settings please refere to 
  http://jtds.sourceforge.net/faq.html
and specify a custom connection string.

JDBC has nothing to do with ODBC, we only use the ODBC/JDBC bridge for MS Access.