ConnectionStrings.com - How to connect to SQL Server 2005

导读：
　　 Where do youwant to connect?
　　 What is a connection string?
　　 Are there any important rulesthat applies to connection strings?
　　 Why can't my app connect?
　　This is a compiled connection strings reference list on how to connect to SQL Server 2005.
　　 Looking for SQL Server 2005 CE connection strings? They are here >>
　　 Looking for SQL Server connection strings? They are here >>
　　 SQL Native Client ODBC Driver
　　 Standard security
　　Driver={SQL Native Client}Server=myServerAddressDatabase=myDataBaseUid=myUsernamePwd=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
　　Driver={SQL Native Client}Server=myServerAddressDatabase=myDataBaseTrusted_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 Native Client}Server=myServerName/theInstanceNameDatabase=myDataBaseTrusted_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") = adPromptAlwaysDriver={SQL Native Client}Server=myServerAddressDatabase=myDataBase
　　 Enabling MARS (multiple active result sets)
　　Driver={SQL Native Client}Server=myServerAddressDatabase=myDataBaseTrusted_Connection=yesMARS_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
　　Driver={SQL Native Client}Server=myServerAddressDatabase=myDataBaseTrusted_Connection=yesEncrypt=yes
　　 Attach a database file on connect to a local SQL Server Express instance
　　Driver={SQL Native Client}Server=./SQLExpressAttachDbFilename=c:/asd/qwe/mydbfile.mdfDatabase=dbnameTrusted_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 Native Client}Server=./SQLExpressAttachDbFilename=|DataDirectory|mydbfile.mdfDatabase=dbnameTrusted_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.
　　Data Source=myServerAddressFailover Partner=myMirrorServerInitial Catalog=myDataBaseIntegrated 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 Native Client OLE DB Provider
　　 Standard security
　　Provider=SQLNCLIServer=myServerAddressDatabase=myDataBaseUid=myUsernamePwd=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
　　Provider=SQLNCLIServer=myServerAddressDatabase=myDataBaseTrusted_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=SQLNCLIServer=myServerName/theInstanceNameDatabase=myDataBaseTrusted_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") = adPromptAlwaysoConn.Open "Provider=SQLNCLIServer=myServerAddressDataBase=myDataBase
　　 Enabling MARS (multiple active result sets)
　　Provider=SQLNCLIServer=myServerAddressDatabase=myDataBaseTrusted_Connection=yesMarsConn=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
　　Provider=SQLNCLIServer=myServerAddressDatabase=myDataBaseTrusted_Connection=yesEncrypt=yes
　　 Attach a database file on connect to a local SQL Server Express instance
　　Provider=SQLNCLIServer=./SQLExpressAttachDbFilename=c:/asd/qwe/mydbfile.mdfDatabase=dbnameTrusted_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=SQLNCLIServer=./SQLExpressAttachDbFilename=|DataDirectory|mydbfile.mdfDatabase=dbnameTrusted_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.
　　Data Source=myServerAddressFailover Partner=myMirrorServerInitial Catalog=myDataBaseIntegrated 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.
　　 SqlConnection (.NET)
　　 Standard Security
　　Data Source=myServerAddressInitial Catalog=myDataBaseUser Id=myUsernamePassword=myPassword
　　Use serverName/instanceName as Data Source to connect to a specific SQL Server instance.
　　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.
　　 Standard Security alternative syntax
　　This connection string produce the same result as the previous one. The reason to include it is to point out that some connection string keywords have many equivalents.
　　Server=myServerAddressDatabase=myDataBaseUser ID=myUsernamePassword=myPasswordTrusted_Connection=False
　　 Trusted Connection
　　Data Source=myServerAddressInitial Catalog=myDataBaseIntegrated Security=SSPI
　　 Trusted Connection alternative syntax
　　This connection string produce the same result as the previous one. The reason to include it is to point out that some connection string keywords have many equivalents.
　　Server=myServerAddressDatabase=myDataBaseTrusted_Connection=True
　　 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.
　　Server=myServerName/theInstanceNameDatabase=myDataBaseTrusted_Connection=True
　　 Trusted Connection from a CE device
　　Often a Windows CE device is not authenticated and logged in to a domain. To use SSPI or trusted connection / authentication from a CE device, use this connection string.
　　Data Source=myServerAddressInitial Catalog=myDataBaseIntegrated Security=SSPIUser ID=myDomain/myUsernamePassword=myPassword
　　Note that this will only work on a CE device.
　　 Connect via an IP address
　　Data Source=190.190.200.100,1433Network Library=DBMSSOCNInitial Catalog=myDataBaseUser ID=myUsernamePassword=myPassword
　　DBMSSOCN=TCP/IP. This is how to use TCP/IP instead of Named Pipes. At the end of the Data Source is the port to use. 1433 is the default port for SQL Server.
　　 Enabling MARS (multiple active result sets)
　　Server=myServerAddressDatabase=myDataBaseTrusted_Connection=TrueMultipleActiveResultSets=true
　　Use ADO.NET 2.0 for MARS functionality. MARS is not supported in ADO.NET 1.0 nor ADO.NET 1.1.
　　 Attach a database file on connect to a local SQL Server Express instance
　　Server=./SQLExpressAttachDbFilename=c:/asd/qwe/mydbfile.mdfDatabase=dbnameTrusted_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
　　Server=./SQLExpressAttachDbFilename=|DataDirectory|mydbfile.mdfDatabase=dbnameTrusted_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.
　　 Using an User Instance on a local SQL Server Express instance
　　The User Instance functionality creates a new SQL Server instance on the fly during connect. This works only on a local SQL Server 2005 instance and only when connecting using windows authentication over local named pipes. The purpose is to be able to create a full rights SQL Server instance to a user with limited administrative rights on the computer.
　　Data Source=./SQLExpressIntegrated Security=trueAttachDbFilename=|DataDirectory|/mydb.mdfUser Instance=true
　　To use the User Instance functionality you need to enable it on the SQL Server. This is done by executing the following command: sp_configure 'user instances enabled', '1'. To disable the functionality execute sp_configure 'user instances enabled', '0'.
　　 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.
　　Data Source=myServerAddressFailover Partner=myMirrorServerInitial Catalog=myDataBaseIntegrated 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.
　　 Asynchronous processing
　　A connection to SQL Server 2005 that allows for the issuing of async requests through ADO.NET objects.
　　Server=myServerAddressDatabase=myDataBaseIntegrated Security=TrueAsynchronous Processing=True
　　 SQL Server 2005 specials
　　 Context Connection
　　Connecting to "self" from within your CLR stored prodedure/function. The context connection lets you execute Transact-SQL statements in the same context (connection) that your code was invoked in the first place.
　　 C#
　　using(SqlConnection connection = new SqlConnection("context connection=true"))
　　{
　　connection.Open();
　　// Use the connection
　　}
　　 VB.Net
　　Using connection as new SqlConnection("context connection=true")
　　connection.Open()
　　' Use the connection
　　End Using

本文转自
http://www.connectionstrings.com/?carrier=sqlserver2005