SQL Server 2005
This is a compiled connection strings reference list on how to connect to SQL Server 2005.
SQL Native Client ODBC Driver
Standard security
Quote:
|
Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase ;Uid=myUsername;Pwd=myPassword;
|
If you are using SQL Server 2005 Express, don't miss the server name syntax Servername\SQLEXPRESS where you substitute Servername with the name of the computer where the SQL Server 2005 Express installation resides.
Trusted Connection
Quote:
|
Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase ;Trusted_Connection=yes;
|
Equivalent key-value pair: "Integrated Security=SSPI" equals "Trusted_Connection=yes"
Prompt for username and password
This one is a bit tricky. First you need to set the connection object's Prompt property to adPromptAlways. Then use the connection string to connect to the database.
Quote:
oConn.Properties("Prompt") = adPromptAlways
Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase ;
|
Enabling MARS (multiple active result sets)
Quote:
|
Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase ;Trusted_Connection=yes;MARS_Connection=yes;
|
Equivalent key-value pair: "MultipleActiveResultSets=true" equals "MARS_Connection=yes"
Use ADO.NET 2.0 for MARS functionality. MARS is not supported in ADO.NET 1.0 nor ADO.NET 1.1.
Encrypt data sent over network
Quote:
|
Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase ;Trusted_Connection=yes;Encrypt=yes;
|
Attach a database file on connect to a local SQL Server Express instance
Quote:
|
Driver={SQL Native Client};Server=.\SQLExpress;AttachDbFilename=c:\ab c\xyz\mydbfile.mdf;Database=dbname;Trusted_Connect ion=Yes;
|
Why is the Database parameter needed? If the named database have already been attached, SQL Server does not reattach it. It uses the attached database as the default for the connection.
Attach a database file, located in the data directory, on connect to a local SQL Server Express instance
Quote:
|
Driver={SQL Native Client};Server=.\SQLExpress;AttachDbFilename=|Data Directory|mydbfile.mdf;Database=dbname;Trusted_Con nection=Yes;
|
Why is the Database parameter needed? If the named database has already been attached, SQL Server does not reattach it. It uses the attached database as the default for the connection.
Database mirroring
If you connect with ADO.NET or the SQL Server Native Client to a database that is being mirrored, your application can take advantage of the drivers ability to automatically redirect connections when a database mirroring failover occurs. You must specify the initial principal server and database in the connection string and the failover partner server.
Quote:
|
Data Source=myServerAddress;Failover Partner=myMirrorServer;Initial Catalog=myDataBase;Integrated Security=True;
|
There is ofcourse many other ways to write the connection string using database mirroring, this is just one example pointing out the failover functionality.
SQL Native Client OLE DB Provider
Standard security
Quote:
|
Provider=SQLNCLI;Server=myServerAddress;Database=m yDataBase;Uid=myUsername;Pwd=myPassword;
|
Are you using SQL Server 2005 Express? Don't miss the server name syntax Servername\SQLEXPRESS where you substitute Servername with the name of the computer where the SQL Server 2005 Express installation resides.
Trusted connection
Quote:
|
Provider=SQLNCLI;Server=myServerAddress;Database=m yDataBase;Trusted_Connection=yes;
|
Equivalent key-value pair: "Integrated Security=SSPI" equals "Trusted_Connection=yes"
Prompt for username and password
This one is a bit tricky. First you need to set the connection object's Prompt property to adPromptAlways. Then use the connection string to connect to the database.
Quote:
oConn.Properties("Prompt") = adPromptAlways
oConn.Open "Provider=SQLNCLI;Server=myServerAddress;DataBase=m yDataBase;
|
Enabling MARS (multiple active result sets)
Quote:
|
Provider=SQLNCLI;Server=myServerAddress;Database=m yDataBase;Trusted_Connection=yes;MarsConn=yes;
|
Equivalent key-value pair: "MultipleActiveResultSets=true" equals "MARS_Connection=yes"
Use ADO.NET 2.0 for MARS functionality. MARS is not supported in ADO.NET 1.0 nor ADO.NET 1.1.
Encrypt data sent over network
Quote:
|
Provider=SQLNCLI;Server=myServerAddress;Database=m yDataBase;Trusted_Connection=yes;Encrypt=yes;
|
Attach a database file on connect to a local SQL Server Express instance
Quote:
|
Provider=SQLNCLI;Server=.\SQLExpress;AttachDbFilen ame=c:\asd\qwe\mydbfile.mdf;Database=dbname;Truste d_Connection=Yes;
|
Why is the Database parameter needed? If the named database have already been attached, SQL Server does not reattach it. It uses the attached database as the default for the connection.
Attach a database file, located in the data directory, on connect to a local SQL Server Express instance
Quote:
|
Provider=SQLNCLI;Server=.\SQLExpress;AttachDbFilen ame=|DataDirectory|mydbfile.mdf;Database=dbname;Tr usted_Connection=Yes;
|
Why is the Database parameter needed? If the named database have already been attached, SQL Server does not reattach it. It uses the attached database as the default for the connection.
Database mirroring
If you connect with ADO.NET or the SQL Server Native Client to a database that is being mirrored, your application can take advantage of the drivers ability to automatically redirect connections when a database mirroring failover occurs. You must specify the initial principal server and database in the connection string and the failover partner server.
Quote:
|
Data Source=myServerAddress;Failover Partner=myMirrorServer;Initial Catalog=myDataBase;Integrated Security=True;
|
There are many other ways to write the connection string using database mirroring, this is just one example pointing out the failover functionality. You can combine this with the other connection strings options available.
Please refer the following URL for MSSQL 2000 connection strings:
MSSQL 2000 connection strings