Connection strings for SQL Server 2008

SQL Server Native Client 10.0 OLE DB Provider

Type:    OLE DB Provider
Usage:  Provider=SQLNCLI10

Manufacturer:  Microsoft
More info about this provider »

Customize string
example values »

Standard security

Provider= SQLNCLI10; Server= myServerAddress; Database= myDataBase; Uid= myUsername;  Pwd= myPassword;

Are you using SQL Server 2008 Express? Don't miss the server name syntax Servername/SQLEXPRESS where you substitute Servername with the name of the computer where the SQL Server 2008 Express installation resides.

 

Trusted connection

Provider= SQLNCLI10; Server= myServerAddress; Database= myDataBase;  Trusted_Connection= yes;

Equivalent key-value pair: "Integrated Security=SSPI" equals "Trusted_Connection=yes"

 

Connecting to an SQL Server instance

The syntax of specifying the server instance in the value of the server key is the same for all connection strings for SQL Server.

Provider= SQLNCLI10; Server= myServerName/theInstanceName; Database= myDataBase; 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.

oConn.Properties("Prompt") = adPromptAlways

oConn.Open "Provider= SQLNCLI10; Server= myServerAddress; DataBase= myDataBase;

 

 

Enabling MARS (multiple active result sets)

Provider= SQLNCLI10; Server= myServerAddress; Database= myDataBase;  Trusted_Connection= yes; MARS Connection= True;

Use ADO.NET for MARS functionality. MARS is not supported in ADO.NET 1.0 nor ADO.NET 1.1.

Using MARS with SQL Native Client, by Chris Lee

 

Encrypt data sent over network

Provider= SQLNCLI10; Server= myServerAddress; Database= myDataBase; Trusted_Connection= yes; Encrypt= yes;

 

 

Attach a database file on connect to a local SQL Server Express instance

Provider= SQLNCLI10; Server= ./SQLExpress; AttachDbFilename= c:/asd/qwe/mydbfile.mdf; Database= dbname;  Trusted_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

Provider= SQLNCLI10; Server= ./SQLExpress; AttachDbFilename= |DataDirectory|mydbfile.mdf; Database= dbname; Trusted_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 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.

Provider= SQLNCLI10; Data Source= myServerAddress; Failover Partner= myMirrorServerAddress; 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. You can combine this with the other connection strings options available.

SQL Server Native Client 10.0 ODBC Driver

Type:    ODBC Driver
Usage:  Driver={SQL Server Native Client 10.0}

Manufacturer:  Microsoft
More info about this driver »

Customize string
example values »

Standard security

Driver= {SQL Server Native Client 10.0}; Server= myServerAddress; Database= myDataBase; Uid= myUsername; Pwd= myPassword;

Are you using SQL Server 2008 Express? Don't miss the server name syntax Servername/SQLEXPRESS where you substitute Servername with the name of the computer where the SQL Server 2008 Express installation resides.

 

Trusted Connection

Driver= {SQL Server Native Client 10.0}; Server= myServerAddress; Database= myDataBase; Trusted_Connection= yes;

Equivalent key-value pair: "Integrated Security=SSPI" equals "Trusted_Connection=yes"

 

Connecting to an SQL Server instance

The syntax of specifying the server instance in the value of the server key is the same for all connection strings for SQL Server.

Driver= {SQL Server Native Client 10.0}; Server= myServerName/theInstanceName; Database= myDataBase; 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.

oConn.Properties("Prompt") = adPromptAlways

Driver= {SQL Server Native Client 10.0}; Server= myServerAddress; Database= myDataBase;

 

 

Enabling MARS (multiple active result sets)

Driver= {SQL Server Native Client 10.0}; Server= myServerAddress; Database= myDataBase; Trusted_Connection= yes;  MARS_Connection= yes;

Use ADO.NET for MARS functionality. MARS is not supported in ADO.NET 1.0 nor ADO.NET 1.1.

Using MARS with SQL Native Client, by Chris Lee

 

Encrypt data sent over network

Driver= {SQL Server Native Client 10.0}; Server= myServerAddress; Database= myDataBase; Trusted_Connection= yes; Encrypt= yes;

 

 

Attach a database file on connect to a local SQL Server Express instance

Driver= {SQL Server Native Client 10.0}; Server= ./SQLExpress; AttachDbFilename= c:/asd/qwe/mydbfile.mdf;  Database= dbname; Trusted_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

Driver= {SQL Server Native Client 10.0}; Server= ./SQLExpress; AttachDbFilename= |DataDirectory|mydbfile.mdf; Database= dbname; Trusted_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 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.

Driver= {SQL Server Native Client 10.0}; Server= myServerAddress; Failover_Partner= myMirrorServerAddress; Database= myDataBase; Trusted_Connection= yes;

There is ofcourse 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 note if you are using TCP/IP (using the network library parameter) and database mirroring, including port number in the address (formed as servername,portnumber) for booth the main server and the failover partner can solve some reported issues.

 

 

文章出处：http://www.connectionstrings.com/sql-server-2008