MSDataShape
.NET Framework Data Provider for OLE DB
.NET Framework Data Provider for ODBC
The
server/instance
name syntax used in the
server
option is the same for all SQL Server connection strings.
Server
=
myServerName\myInstanceName;
Database
=
myDataBase;
User Id
=
myUsername;
Password
=
myPassword;
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it's not a colon).
Server
=
myServerName,myPortNumber;
Database
=
myDataBase;
User Id
=
myUsername;
Password
=
myPassword;
Data Source
=
190.190.200.100,1433;
Network Library
=
DBMSSOCN;
Initial Catalog
=
myDataBase;
User ID
=
myUsername;
Password
=
myPassword;
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
True;
MultipleActiveResultSets
=
true;
Server
=
.\SQLExpress;
AttachDbFilename
=
C:\MyFolder\MyDataFile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
Server
=
.\SQLExpress;
AttachDbFilename
=
|DataDirectory|mydbfile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
The
User Instance
feature is deprecated with SQL Server 2012, use the
SQL Server Express LocalDB
feature instead.
Server
=
(localdb)\v11.0;
Integrated Security
=
true;
AttachDbFileName
=
C:\MyFolder\MyData.mdf;
To create a named instance, use the
SqlLocalDB.exe
program. Example
SqlLocalDB.exe create MyInstance
and
SqlLocalDB.exe start MyInstance
Server
=
(localdb)\MyInstance;
Integrated Security
=
true;
The
Server=(localdb)
syntax is not supported by .NET framework versions before 4.0.2. However the named pipes connection will work to connect pre 4.0.2 applications to LocalDB instances.
Server
=
np:\\.\pipe\LOCALDB#F365A78E\tsql\query;
Both automatic and named instances of LocalDB can be shared.
Server
=
(localdb)\.\MyInstanceShare;
Integrated Security
=
true;
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
=
myServerAddress;
Failover Partner
=
myMirrorServerAddress;
Initial Catalog
=
myDataBase;
Integrated Security
=
True;
A connection to SQL Server that allows for the issuing of async requests through ADO.NET objects.
Server
=
myServerAddress;
Database
=
myDataBase;
Integrated Security
=
True;
Asynchronous Processing
=
True;
The User Instance functionality creates a new SQL Server instance on the fly during connect. This works only on a local SQL Server 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
=
C:\MyFolder\MyDataFile.mdf;
User Instance
=
true;
Server
=
myServerAddress;
Database
=
myDataBase;
User ID
=
myUsername;
Password
=
myPassword;
Trusted_Connection
=
False;
Packet Size
=
4096;
Data Source
=
myServer;
Initial Catalog
=
myDB;
Integrated Security
=
true;
Column Encryption Setting
=
enabled;
Data Source
=
myServer;
Initial Catalog
=
myDB;
Integrated Security
=
true;
Column Encryption Setting
=
enabled;
Enclave Attestation Url
=
http://hgs.bastion.local/Attestation;
The
server/instance
name syntax used in the
server
option is the same for all SQL Server connection strings.
Server
=
myServerName\myInstanceName;
Database
=
myDataBase;
User Id
=
myUsername;
Password
=
myPassword;
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it's not a colon).
Server
=
myServerName,myPortNumber;
Database
=
myDataBase;
User Id
=
myUsername;
Password
=
myPassword;
A Windows CE device is most often not authenticated and logged in to a domain but it is possible to use SSPI or trusted connection and authentication from a CE device using this connection string.
Data Source
=
myServerAddress;
Initial Catalog
=
myDataBase;
Integrated Security
=
SSPI;
User ID
=
myDomain\myUsername;
Password
=
myPassword;
Data Source
=
190.190.200.100,1433;
Network Library
=
DBMSSOCN;
Initial Catalog
=
myDataBase;
User ID
=
myUsername;
Password
=
myPassword;
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
True;
MultipleActiveResultSets
=
true;
Server
=
.\SQLExpress;
AttachDbFilename
=
C:\MyFolder\MyDataFile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
Server
=
.\SQLExpress;
AttachDbFilename
=
|DataDirectory|mydbfile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
The
User Instance
feature is deprecated with SQL Server 2012, use the
SQL Server Express LocalDB
feature instead.
Server
=
(localdb)\v11.0;
Integrated Security
=
true;
AttachDbFileName
=
C:\MyFolder\MyData.mdf;
To create a named instance, use the
SqlLocalDB.exe
program. Example
SqlLocalDB.exe create MyInstance
and
SqlLocalDB.exe start MyInstance
Server
=
(localdb)\MyInstance;
Integrated Security
=
true;
The
Server=(localdb)
syntax is not supported by .NET framework versions before 4.0.2. However the named pipes connection will work to connect pre 4.0.2 applications to LocalDB instances.
Server
=
np:\\.\pipe\LOCALDB#F365A78E\tsql\query;
Both automatic and named instances of LocalDB can be shared.
Server
=
(localdb)\.\MyInstanceShare;
Integrated Security
=
true;
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
=
myServerAddress;
Failover Partner
=
myMirrorServerAddress;
Initial Catalog
=
myDataBase;
Integrated Security
=
True;
A connection to SQL Server that allows for the issuing of async requests through ADO.NET objects.
Server
=
myServerAddress;
Database
=
myDataBase;
Integrated Security
=
True;
Asynchronous Processing
=
True;
The User Instance functionality creates a new SQL Server instance on the fly during connect. This works only on a local SQL Server 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
=
C:\MyFolder\MyDataFile.mdf;
User Instance
=
true;
Server
=
myServerAddress;
Database
=
myDataBase;
User ID
=
myUsername;
Password
=
myPassword;
Trusted_Connection
=
False;
Packet Size
=
4096;
Data Source
=
myServer;
Initial Catalog
=
myDB;
Integrated Security
=
true;
Column Encryption Setting
=
enabled;
Data Source
=
myServer;
Initial Catalog
=
myDB;
Integrated Security
=
true;
Column Encryption Setting
=
enabled;
Enclave Attestation Url
=
http://hgs.bastion.local/Attestation;
For ADO to correctly map SQL Server new datatypes, i.e. XML, UDT, varchar(max), nvarchar(max), and varbinary(max), include DataTypeCompatibility=80; in the connection string. If you are not using ADO this is not necessary.
Provider
=
MSOLEDBSQL;
DataTypeCompatibility
=
80;
Server
=
myServerAddress;
Database
=
myDataBase;
UID
=
myUsername;
PWD
=
myPassword;
Provider
=
MSOLEDBSQL;
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
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
=
MSOLEDBSQL;
Server
=
myServerName\theInstanceName;
Database
=
myDataBase;
Trusted_Connection
=
yes;
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it's not a colon).
Provider
=
MSOLEDBSQL;
Server
=
myServerName,myPortNumber;
Database
=
myDataBase;
UID
=
myUsername;
PWD
=
myPassword;
Provider
=
MSOLEDBSQL;
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
MARS Connection
=
true;
Provider
=
MSOLEDBSQL;
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
Encrypt
=
yes;
Provider
=
MSOLEDBSQL;
Server
=
.\SQLExpress;
AttachDBFilename
=
c:\asd\qwe\mydbfile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
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
=
MSOLEDBSQL;
Data Source
=
myServerAddress;
Failover Partner
=
myMirrorServerAddress;
Initial Catalog
=
myDataBase;
Integrated Security
=
True;
Enable fast failover for Always On Availability Groups and Failover Cluster Instances. TCP is the only supported protocol. Also set an explicit timeout as these scenarios might require more time.
Provider
=
MSOLEDBSQL;
Server
=
tcp:AvailabilityGroupListenerDnsName,1433;
MultiSubnetFailover
=
Yes;
Database
=
MyDB;
Integrated Security
=
SSPI;
Connect Timeout
=
30;
Use a read workload when connecting. Enforces read only at connection time, and also for USE database statements.
Provider
=
MSOLEDBSQL;
Server
=
tcp:AvailabilityGroupListenerDnsName,1433;
MultiSubnetFailover
=
Yes;
ApplicationIntent
=
ReadOnly;
Database
=
MyDB;
Integrated Security
=
SSPI;
Connect Timeout
=
30;
You can either use an availability group listener for Server
OR
the read-only instance name to enforce a specific read-only instance.
Provider
=
MSOLEDBSQL;
Server
=
aKnownReadOnlyInstance;
MultiSubnetFailover
=
Yes;
ApplicationIntent
=
ReadOnly;
Database
=
MyDB;
Integrated Security
=
SSPI;
Connect Timeout
=
30;
Provider
=
SQLNCLI11;
Server
=
myServerAddress;
Database
=
myDataBase;
Uid
=
myUsername;
Pwd
=
myPassword;
Provider
=
SQLNCLI11;
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
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
=
SQLNCLI11;
Server
=
myServerName\theInstanceName;
Database
=
myDataBase;
Trusted_Connection
=
yes;
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it's not a colon).
Provider
=
SQLNCLI11;
Server
=
myServerName,myPortNumber;
Database
=
myDataBase;
Uid
=
myUsername;
Pwd
=
myPassword;
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=SQLNCLI11;Server=myServerAddress;DataBase=myDataBase;"
Provider
=
SQLNCLI11;
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
MARS Connection
=
True;
Provider
=
SQLNCLI11;
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
Encrypt
=
yes;
Provider
=
SQLNCLI11;
Server
=
.\SQLExpress;
AttachDbFilename
=
c:\asd\qwe\mydbfile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
Provider
=
SQLNCLI11;
Server
=
.\SQLExpress;
AttachDbFilename
=
|DataDirectory|mydbfile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
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
=
SQLNCLI11;
Data Source
=
myServerAddress;
Failover Partner
=
myMirrorServerAddress;
Initial Catalog
=
myDataBase;
Integrated Security
=
True;
Provider
=
SQLNCLI10;
Server
=
myServerAddress;
Database
=
myDataBase;
Uid
=
myUsername;
Pwd
=
myPassword;
Provider
=
SQLNCLI10;
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
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;
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it's not a colon).
Provider
=
SQLNCLI10;
Server
=
myServerName,myPortNumber;
Database
=
myDataBase;
Uid
=
myUsername;
Pwd
=
myPassword;
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;"
Provider
=
SQLNCLI10;
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
MARS Connection
=
True;
Provider
=
SQLNCLI10;
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
Encrypt
=
yes;
Provider
=
SQLNCLI10;
Server
=
.\SQLExpress;
AttachDbFilename
=
c:\asd\qwe\mydbfile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
Provider
=
SQLNCLI10;
Server
=
.\SQLExpress;
AttachDbFilename
=
|DataDirectory|mydbfile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
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;
Provider
=
SQLNCLI;
Server
=
myServerAddress;
Database
=
myDataBase;
Uid
=
myUsername;
Pwd
=
myPassword;
Provider
=
SQLNCLI;
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
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
=
myDataBase;
Trusted_Connection
=
yes;
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it's not a colon).
Provider
=
SQLNCLI;
Server
=
myServerName,myPortNumber;
Database
=
myDataBase;
Uid
=
myUsername;
Pwd
=
myPassword;
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=myServerAddress;DataBase=myDataBase;"
Provider
=
SQLNCLI;
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
MARS Connection
=
True;
Provider
=
SQLNCLI;
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
Encrypt
=
yes;
Provider
=
SQLNCLI;
Server
=
.\SQLExpress;
AttachDbFilename
=
c:\mydbfile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
Provider
=
SQLNCLI;
Server
=
.\SQLExpress;
AttachDbFilename
=
|DataDirectory|mydbfile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
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
=
myServerAddress;
Failover Partner
=
myMirrorServerAddress;
Initial Catalog
=
myDataBase;
Integrated Security
=
True;
Provider
=
sqloledb;
Data Source
=
myServerAddress;
Initial Catalog
=
myDataBase;
Integrated Security
=
SSPI;
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
=
sqloledb;
Data Source
=
myServerName\theInstanceName;
Initial Catalog
=
myDataBase;
Integrated Security
=
SSPI;
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it's not a colon).
Provider
=
sqloledb;
Server
=
myServerName,myPortNumber;
Database
=
myDataBase;
User Id
=
myUsername;
Password
=
myPassword;
This one is a bit tricky. First set the connection object's Provider property to "sqloledb". Thereafter set the connection object's Prompt property to adPromptAlways. Then use the connection string to connect to the database.
oConn.Provider = "sqloledb"
oConn.Properties("Prompt") = adPromptAlways
oConn.Open "Data Source=myServerAddress;Initial Catalog=myDataBase;"
Provider
=
sqloledb;
Data Source
=
190.190.200.100,1433;
Network Library
=
DBMSSOCN;
Initial Catalog
=
myDataBase;
User ID
=
myUsername;
Password
=
myPassword;
This one is usefull when receving errors "sp_setapprole was not invoked correctly." (7.0) or "General network error. Check your network documentation" (2000) when connecting using an application role enabled connection. Application pooling (or OLE DB resource pooling) is on by default. Disabling it can help on this error.
Provider
=
sqloledb;
Data Source
=
myServerAddress;
Initial Catalog
=
myDataBase;
User ID
=
myUsername;
Password
=
myPassword;
OLE DB Services
=
-2;
Driver
=
{ODBC Driver 17 for SQL Server};
Server
=
myServerAddress;
Database
=
myDataBase;
UID
=
myUsername;
PWD
=
myPassword;
Driver
=
{ODBC Driver 17 for SQL Server};
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
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
=
{ODBC Driver 17 for SQL Server};
Server
=
serverName\instanceName;
Database
=
myDataBase;
Trusted_Connection
=
yes;
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it's not a colon).
Driver
=
{ODBC Driver 17 for SQL Server};
Server
=
myServerName,myPortNumber;
Database
=
myDataBase;
UID
=
myUsername;
PWD
=
myPassword;
Driver
=
{ODBC Driver 17 for SQL Server};
Server
=
serverAddress;
Database
=
databaseName;
Trusted_Connection
=
yes;
MARS_Connection
=
yes;
Driver
=
{ODBC Driver 17 for SQL Server};
Server
=
serverAddress;
Database
=
databaseName;
Trusted_Connection
=
yes;
Encrypt
=
yes;
Driver
=
{ODBC Driver 17 for SQL Server};
Server
=
.\SQLExpress;
AttachDBFileName
=
c:\dir\\mydb.mdf;
Database
=
dbName;
Trusted_Connection
=
yes;
If you connect 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
=
{ODBC Driver 17 for SQL Server};
Server
=
myServerAddress;
Failover_Partner
=
myMirrorServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
Driver
=
{ODBC Driver 13 for SQL Server};
Server
=
myServerAddress;
Database
=
myDataBase;
UID
=
myUsername;
PWD
=
myPassword;
Driver
=
{ODBC Driver 13 for SQL Server};
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
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
=
{ODBC Driver 13 for SQL Server};
Server
=
serverName\instanceName;
Database
=
myDataBase;
Trusted_Connection
=
yes;
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it's not a colon).
Driver
=
{ODBC Driver 13 for SQL Server};
Server
=
myServerName,myPortNumber;
Database
=
myDataBase;
UID
=
myUsername;
PWD
=
myPassword;
Driver
=
{ODBC Driver 13 for SQL Server};
Server
=
serverAddress;
Database
=
databaseName;
Trusted_Connection
=
yes;
MARS_Connection
=
yes;
Driver
=
{ODBC Driver 13 for SQL Server};
Server
=
serverAddress;
Database
=
databaseName;
Trusted_Connection
=
yes;
Encrypt
=
yes;
Driver
=
{ODBC Driver 13 for SQL Server};
Server
=
.\SQLExpress;
AttachDBFileName
=
c:\dir\\mydb.mdf;
Database
=
dbName;
Trusted_Connection
=
yes;
If you connect 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
=
{ODBC Driver 13 for SQL Server};
Server
=
myServerAddress;
Failover_Partner
=
myMirrorServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
Driver
=
{ODBC Driver 11 for SQL Server};
Server
=
myServerAddress;
Database
=
myDataBase;
UID
=
myUsername;
PWD
=
myPassword;
Driver
=
{ODBC Driver 11 for SQL Server};
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
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
=
{ODBC Driver 11 for SQL Server};
Server
=
serverName\instanceName;
Database
=
myDataBase;
Trusted_Connection
=
yes;
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it's not a colon).
Driver
=
{ODBC Driver 11 for SQL Server};
Server
=
myServerName,myPortNumber;
Database
=
myDataBase;
UID
=
myUsername;
PWD
=
myPassword;
Driver
=
{ODBC Driver 11 for SQL Server};
Server
=
serverAddress;
Database
=
databaseName;
Trusted_Connection
=
yes;
MARS_Connection
=
yes;
Driver
=
{ODBC Driver 11 for SQL Server};
Server
=
serverAddress;
Database
=
databaseName;
Trusted_Connection
=
yes;
Encrypt
=
yes;
Driver
=
{ODBC Driver 11 for SQL Server};
Server
=
.\SQLExpress;
AttachDBFileName
=
c:\dir\\mydb.mdf;
Database
=
dbName;
Trusted_Connection
=
yes;
If you connect 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
=
{ODBC Driver 11 for SQL Server};
Server
=
myServerAddress;
Failover_Partner
=
myMirrorServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
Driver
=
{SQL Server Native Client 11.0};
Server
=
myServerAddress;
Database
=
myDataBase;
Uid
=
myUsername;
Pwd
=
myPassword;
Driver
=
{SQL Server Native Client 11.0};
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
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 11.0};
Server
=
myServerName\theInstanceName;
Database
=
myDataBase;
Trusted_Connection
=
yes;
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it's not a colon).
Driver
=
{SQL Server Native Client 11.0};
Server
=
myServerName,myPortNumber;
Database
=
myDataBase;
Uid
=
myUsername;
Pwd
=
myPassword;
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 "Driver={SQL Server Native Client 11.0};Server=myServerAddress;Database=myDataBase;"
Driver
=
{SQL Server Native Client 11.0};
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
MARS_Connection
=
yes;
Driver
=
{SQL Server Native Client 11.0};
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
Encrypt
=
yes;
Driver
=
{SQL Server Native Client 11.0};
Server
=
.\SQLExpress;
AttachDbFilename
=
c:\asd\qwe\mydbfile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
Driver
=
{SQL Server Native Client 11.0};
Server
=
.\SQLExpress;
AttachDbFilename
=
|DataDirectory|mydbfile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
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 11.0};
Server
=
myServerAddress;
Failover_Partner
=
myMirrorServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
Driver
=
{SQL Server Native Client 10.0};
Server
=
myServerAddress;
Database
=
myDataBase;
Uid
=
myUsername;
Pwd
=
myPassword;
Driver
=
{SQL Server Native Client 10.0};
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
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;
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it's not a colon).
Driver
=
{SQL Server Native Client 10.0};
Server
=
myServerName,myPortNumber;
Database
=
myDataBase;
Uid
=
myUsername;
Pwd
=
myPassword;
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 "Driver={SQL Server Native Client 10.0};Server=myServerAddress;Database=myDataBase;"
Driver
=
{SQL Server Native Client 10.0};
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
MARS_Connection
=
yes;
Driver
=
{SQL Server Native Client 10.0};
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
Encrypt
=
yes;
Driver
=
{SQL Server Native Client 10.0};
Server
=
.\SQLExpress;
AttachDbFilename
=
c:\asd\qwe\mydbfile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
Driver
=
{SQL Server Native Client 10.0};
Server
=
.\SQLExpress;
AttachDbFilename
=
|DataDirectory|mydbfile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
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;
Driver
=
{SQL Native Client};
Server
=
myServerAddress;
Database
=
myDataBase;
Uid
=
myUsername;
Pwd
=
myPassword;
Driver
=
{SQL Native Client};
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
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
=
myDataBase;
Trusted_Connection
=
yes;
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it's not a colon).
Driver
=
{SQL Native Client};
Server
=
myServerName,myPortNumber;
Database
=
myDataBase;
Uid
=
myUsername;
Pwd
=
myPassword;
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 "Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase;"
Driver
=
{SQL Native Client};
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
MARS_Connection
=
yes;
Driver
=
{SQL Native Client};
Server
=
myServerAddress;
Database
=
myDataBase;
Trusted_Connection
=
yes;
Encrypt
=
yes;
Driver
=
{SQL Native Client};
Server
=
.\SQLExpress;
AttachDbFilename
=
c:\mydbfile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
Driver
=
{SQL Native Client};
Server
=
.\SQLExpress;
AttachDbFilename
=
|DataDirectory|mydbfile.mdf;
Database
=
dbname;
Trusted_Connection
=
Yes;
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;
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it's not a colon).
Driver
=
{SQL Server};
Server
=
myServerName,myPortNumber;
Database
=
myDataBase;
Uid
=
myUsername;
Pwd
=
myPassword;
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 "Driver={SQL Server};Server=myServerAddress;Database=myDataBase;"
The DataTypeCompatibility=80 is important for the XML types to be recognised by ADO.
Provider
=
SQLXMLOLEDB.4.0;
Data Provider
=
MSOLEDBSQL;
DataTypeCompatibility
=
80;
Data Source
=
myServerAddress;
Initial Catalog
=
myDataBase;
User Id
=
myUsername;
Password
=
myPassword;
Provider
=
SQLXMLOLEDB.4.0;
Data Provider
=
SQLNCLI11;
Data Source
=
myServerAddress;
Initial Catalog
=
myDataBase;
User Id
=
myUsername;
Password
=
myPassword;
Provider
=
SQLXMLOLEDB.4.0;
Data Provider
=
SQLNCLI10;
Data Source
=
myServerAddress;
Initial Catalog
=
myDataBase;
User Id
=
myUsername;
Password
=
myPassword;
Provider
=
SQLXMLOLEDB.4.0;
Data Provider
=
SQLNCLI;
Data Source
=
myServerAddress;
Initial Catalog
=
myDataBase;
User Id
=
myUsername;
Password
=
myPassword;
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.
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
Provider
=
MSDataShape;
Data Provider
=
SQLOLEDB;
Data Source
=
myServerAddress;
Initial Catalog
=
myDataBase;
User ID
=
myUsername;
Password
=
myPassword;
Connect to
