MS SQL Server
Using SQL Security
Provider=sqloledb; Data Source=locahost; Initial Catalog=database; User ID=username; Password=password;
Using Windows Integrated Security
Provider=sqloledb; Server=localhost; Database=database; Integrated Security=SSPI; Persist Security Info=False;
MySQL
Using MyODBC version 3.5.1
DRIVER={MySQL ODBC 3.51 Driver}; SERVER=localhost; DATABASE=database; UID=username; PWD=password; OPTION=connection-options;
| MySQL 5.* | Stronger password encryption implemented in version 5 are not compatible with MyODBC 3.5.1. As version 5 is non production, these problems can be worked around by using a login with a blank password and the omission of the PWD section in the connection string. |
| .Net | Whilst connecting with .Net using the ODBCConnection object, I needed to remove the spaces after the semi-colons in the connection string - very odd! |
253 comments,
Database, Sunday, March 14, 2004 13:38
