Connection strings for SQL Server 2005

in my previous article, I was asked to give a tutorial on sql server and vb.net connection. in this case i use SQL Server 2005 Standard edition.

so this is all connections strings providers for SQL Server 2005
Note : I assumed that you already installed SQL Server and Visual studio also use
this setting :

Server address  
Database name  
Username  
Password 

"adevla" was my localhost username XD

.NET Framework Data Provider for SQL Server

TYPE .NET Framework Class LibraryUSAGE System.Data.SqlClient.SqlConnectionMANUFACTURER Microsoft

Standard Security

Data Source=10.252.108.103;Initial Catalog=SQLServ2005;User Id=adelva;Password=p@ssw0rd;

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.

COPY

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=10.252.108.103;Database=SQLServ2005;User ID=adelva;Password=p@ssw0rd;Trusted_Connection=False;

COPY

Trusted Connection

Data Source=10.252.108.103;Initial Catalog=SQLServ2005;Integrated Security=SSPI;

COPY

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=10.252.108.103;Database=SQLServ2005;Trusted_Connection=True;

COPY

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\theInstanceName;Database=SQLServ2005;Trusted_Connection=True;

COPY

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=10.252.108.103;Initial Catalog=SQLServ2005;Integrated Security=SSPI;User ID=myDomain\myUsername;Password=myPassword;

Note that this will only work on a CE device.

Connect via an IP address

Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=SQLServ2005;User ID=adelva;Password=p@ssw0rd;

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.

How to define which network protocol to use

COPY

Enabling MARS (multiple active result sets)

Server=10.252.108.103;Database=SQLServ2005;Trusted_Connection=True; MultipleActiveResultSets=true;

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

Streamline your Data Connections by Moving to MARS, by Laurence Moroney, DevX.com

COPY

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

Server=.\SQLExpress;AttachDbFilename=c:\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.

COPY

Attach a database file, located in the data directory, on connect to a local SQL Server Express instance

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.

COPY

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=.\SQLExpress;Integrated Security=true; AttachDbFilename=|DataDirectory|\mydb.mdf;User 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'.

COPY

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=10.252.108.103;Failover Partner=myMirrorServerAddress;Initial Catalog=SQLServ2005;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.

Read more about database mirroring in this Microsoft TechNet article "Database Mirroring in SQL Server 2005"

COPY

Asynchronous processing

A connection to SQL Server 2005 that allows for the issuing of async requests through ADO.NET objects.

Server=10.252.108.103;Database=SQLServ2005;Integrated Security=True;Asynchronous Processing=True;

COPY

SQL Native Client 9.0 OLE DB provider

TYPE OLE DB ProviderUSAGE Provider=SQLNCLIMANUFACTURER Microsoft

Standard security

Provider=SQLNCLI;Server=10.252.108.103;Database=SQLServ2005;Uid=adelva;
Pwd=p@ssw0rd;

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=SQLNCLI;Server=10.252.108.103;Database=SQLServ2005;
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=SQLNCLI;Server=myServerName\theInstanceName;Database=SQLServ2005; 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=SQLNCLI;
Server=10.252.108.103;DataBase=SQLServ2005;

Enabling MARS (multiple active result sets)

Provider=SQLNCLI;Server=10.252.108.103;Database=SQLServ2005; Trusted_Connection=yes;MARS Connection=True;

Use ADO.NET 2.0 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=SQLNCLI;Server=10.252.108.103;Database=SQLServ2005; Trusted_Connection=yes;Encrypt=yes;

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

Provider=SQLNCLI;Server=.\SQLExpress;AttachDbFilename=c:\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=SQLNCLI;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.

Download the SQL Native Client here. The package contains booth the ODBC driver and the OLE DB provider

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=SQLNCLI;Data Source=10.252.108.103;Failover Partner=myMirrorServerAddress;Initial Catalog=SQLServ2005;
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.

Read more about database mirroring in this Microsoft TechNet article "Database Mirroring in SQL Server 2005"

.NET Framework Data Provider for OLE DB

TYPE .NET Framework Wrapper Class LibraryUSAGE System.Data.OleDb.OleDbConnectionMANUFACTURER Microsoft

Bridging to SQL Native Client OLE DB

This is just one connection string sample for the wrapping OleDbConnection class that calls the underlying OLEDB provider. See respective OLE DB provider for more connection strings to use with this class.

Provider=SQLNCLI;Server=10.252.108.103;Database=SQLServ2005;
Uid=adelva; Pwd=p@ssw0rd;

SQL Server Native Client 10.0 OLE DB Provider

TYPE OLE DB ProviderUSAGE Provider=SQLNCLI10MANUFACTURER Microsoft

Standard security

Provider=SQLNCLI10;Server=10.252.108.103;Database=SQLServ2005;
Uid=adelva; Pwd=p@ssw0rd;

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=SQLNCLI10;Server=10.252.108.103;Database=SQLServ2005;
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=SQLServ2005; 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=10.252.108.103;
DataBase=SQLServ2005;

Enabling MARS (multiple active result sets)

Provider=SQLNCLI10;Server=10.252.108.103;Database=SQLServ2005; Trusted_Connection=yes;MARS Connection=True;

Use ADO.NET 2.0 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=10.252.108.103;Database=SQLServ2005; Trusted_Connection=yes;Encrypt=yes;

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

Provider=SQLNCLI10;Server=.\SQLExpress;AttachDbFilename=c:\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.

Download the SQL Native Client here. The package contains booth the ODBC driver and the OLE DB provider

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=10.252.108.103;Failover Partner=myMirrorServerAddress;Initial Catalog=SQLServ2005;
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.

Read more about database mirroring in this Microsoft TechNet article "Database Mirroring in SQL Server 2005"

SQL Native Client 9.0 ODBC Driver

TYPE ODBC DriverUSAGE Driver={SQL Native Client}MANUFACTURER Microsoft

Standard security

Driver={SQL Native Client};Server=10.252.108.103;Database=SQLServ2005; Uid=adelva;Pwd=p@ssw0rd;

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.

COPY

Trusted Connection

Driver={SQL Native Client};Server=10.252.108.103;Database=SQLServ2005; Trusted_Connection=yes;

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

COPY

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\theInstanceName;Database=SQLServ2005; Trusted_Connection=yes;

COPY

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 Native Client};Server=10.252.108.103;Database=SQLServ2005;

COPY

Enabling MARS (multiple active result sets)

Driver={SQL Native Client};Server=10.252.108.103;Database=SQLServ2005; Trusted_Connection=yes;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.

Using MARS with SQL Native Client, by Chris Lee

COPY

Encrypt data sent over network

Driver={SQL Native Client};Server=10.252.108.103;Database=SQLServ2005; Trusted_Connection=yes;Encrypt=yes;

COPY

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

Driver={SQL Native Client};Server=.\SQLExpress;AttachDbFilename=c:\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.

COPY

Attach a database file, located in the data directory, on connect to a local SQL Server Express instance

Driver={SQL Native Client};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.

Download the SQL Native Client here. The package contains booth the ODBC driver and the OLE DB provider

COPY

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=10.252.108.103;Failover_Partner=myMirrorServerAddress;Database=SQLServ2005; 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.

Read more about database mirroring in this Microsoft TechNet article "Database Mirroring in SQL Server 2005"

COPY

SQL Server Native Client 10.0 ODBC Driver

TYPE ODBC DriverUSAGE Driver={SQL Server Native Client 10.0}MANUFACTURER Microsoft

Standard security

Driver={SQL Server Native Client 10.0};Server=10.252.108.103;Database=SQLServ2005;Uid=adelva;Pwd=p@ssw0rd;

COPY

Trusted Connection

Driver={SQL Server Native Client 10.0};Server=10.252.108.103;Database=SQLServ2005;Trusted_Connection=yes;

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

COPY

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=SQLServ2005;Trusted_Connection=yes;

COPY

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=10.252.108.103;Database=SQLServ2005;

COPY

Enabling MARS (multiple active result sets)

Driver={SQL Server Native Client 10.0};Server=10.252.108.103;Database=SQLServ2005;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

COPY

Encrypt data sent over network

Driver={SQL Server Native Client 10.0};Server=10.252.108.103;Database=SQLServ2005; Trusted_Connection=yes;Encrypt=yes;

COPY

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.

COPY

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.

COPY

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=10.252.108.103;Failover_Partner=myMirrorServerAddress;Database=SQLServ2005; 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.

Read more about database mirroring in this Microsoft TechNet article "Database Mirroring in SQL Server 2005"

.NET Framework Data Provider for ODBC

TYPE .NET Framework Wrapper Class LibraryUSAGE System.Data.Odbc.OdbcConnectionMANUFACTURER Microsoft

Bridging to SQL Native Client 10.0 ODBC Driver

This is just one connection string sample for the wrapping OdbcConnection class that calls the underlying ODBC Driver. See respective ODBC driver for more connection strings to use with this class.

Driver={SQL Server Native Client 10.0};Server=10.252.108.103;Database=SQLServ2005;Uid=adelva;Pwd=p@ssw0rd;

COPY

SQLXML 4.0 OLEDB Provider

TYPE OLE DB ProviderUSAGE Provider=SQLXMLOLEDB.4.0;Data Provider=providernameMANUFACTURER Microsoft

Using SQL Server Native Client provider

Provider=SQLXMLOLEDB.4.0;Data Provider=SQLNCLI;
Data Source=10.252.108.103;Initial Catalog=SQLServ2005;User Id=adelva;Password=p@ssw0rd;

  

Context Connection

TYPE .NET Framework Class LibraryUSAGE 
MANUFACTURER Microsoft

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