SQL SERVER连接字符串

最新推荐文章于 2022-04-03 09:20:57 发布
最新推荐文章于 2022-04-03 09:20:57 发布
阅读量1.5k 收藏
点赞数
分类专栏： C++ otl
C++ 同时被 2 个专栏收录
51 篇文章 2 订阅
订阅专栏
otl
18 篇文章 0 订阅
订阅专栏

原贴地址：https://www.connectionstrings.com/sql-server/


.NET Framework Data Provider for SQL Server

↯ Problems connecting?
Get answer in the  SQL Server Q & A forum

Context Connection

  • 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

SQL Server Native Client 11.0 OLE DB Provider

  • Standard security

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

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

    When to use SQL Native Client?

  • Trusted connection

    Provider=SQLNCLI11;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=SQLNCLI11;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=SQLNCLI11;Server=myServerAddress;DataBase=myDataBase;"

  • Enable MARS

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

  • Encrypt data sent over network

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

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

    Provider=SQLNCLI11;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=SQLNCLI11;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=SQLNCLI11;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 OLE DB Provider

SQL Native Client 9.0 OLE DB Provider

Microsoft OLE DB Provider for SQL Server

  • Standard Security

    Provider=sqloledb;Data Source=myServerAddress;Initial Catalog=myDataBase;
    User Id    =myUsername;Password=myPassword;

  • Trusted connection

    Provider=sqloledb;Data Source=myServerAddress;Initial Catalog=myDataBase;
    Integrated Security    =SSPI;

    Use serverName\instanceName as Data Source to use a specific SQL Server instance. Please note that the multiple SQL Server instances feature is available only from SQL Server version 2000 and not in any previous versions.

  • 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=sqloledb;Data Source=myServerName\theInstanceName;
    Initial Catalog    =myDataBase;Integrated Security=SSPI;

  • Prompt for username and password

    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;"

  • Connect via an IP address

    Provider=sqloledb;Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;
    Initial Catalog    =myDataBase;User ID=myUsername;Password=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. Read more in the article How to define which network protocol to use.

  • Disable connection pooling

    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;

SQLXML 4.0 OLEDB Provider

SQLXML 3.0 OLEDB Provider

  • Using SQL Server Ole Db

    The SQLXML version 3.0 restricts the data provider to SQLOLEDB only.

    Provider=SQLXMLOLEDB.3.0;Data Provider=SQLOLEDB;Data Source=myServerAddress;
    Initial Catalog    =myDataBase;User Id=myUsername;Password=myPassword;

.NET Framework Data Provider for OLE DB

  • Use an OLE DB provider from .NET

    Provider=any oledb provider's name;OledbKey1=someValue;OledbKey2=someValue;

    See the respective OLEDB provider's connection strings options. The .net OleDbConnection will just pass on the connection string to the specified OLEDB provider. Read more here.

SQL Server Native Client 11.0 ODBC Driver

  • Standard security

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

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

    When to use SQL Native Client?

  • Trusted Connection

    Driver={SQL Server Native Client 11.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 11.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

    oConn.Open "Driver={SQL Server Native Client 11.0};Server=myServerAddress;Database=myDataBase;"

  • Enable MARS

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

  • Encrypt data sent over network

    Driver={SQL Server Native Client 11.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 11.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 11.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 11.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 both the main server and the failover partner can solve some reported issues.

SQL Server Native Client 10.0 ODBC Driver

SQL Native Client 9.0 ODBC Driver

  • Standard security

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

    When to use SQL Native Client?

  • Trusted Connection

    Driver={SQL Native Client};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 Native Client};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 "Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase;"

  • Enable MARS

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

  • Encrypt data sent over network

    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

    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.

  • 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.

  • 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 both the main server and the failover partner can solve some reported issues.

Microsoft SQL Server ODBC Driver

.NET Framework Data Provider for ODBC

  • Use an ODBC driver from .NET

    Driver={any odbc driver's name};OdbcKey1=someValue;OdbcKey2=someValue;

    See the respective ODBC driver's connection strings options. The .net OdbcConnection will just pass on the connection string to the specified ODBC driver. Read more here.

MSDataShape


绝世神棍
关注
专栏目录
SQL Server连接字符串生成工具
05-29
快速生成连接字符串 方便开发人员使用数据库 快速生成连接字符串 方便开发人员使用数据库
SQL Server 连接字符串
weixin_30737363的博客
04-01 118
SQL Native Client ODBC Driver 标准安全连接 Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword; 您是否在使用SQL Server 2005 Express？ 请在“Server”...
SQL Server 连接字符串代码
生活在爪洼岛上
08-19 4098
ODBC 标准连接 Driver={SQL Server};Server=myServerAddress;Database=myDataBase; Uid=myUsername;Pwd=myPassword; 受信的连接 Driver={SQL Server};Server=myServerAddress;Database=myDataBase; Trusted_Connection=Yes;...
SQL Server 连接字符串写法大全
Michael20211212的博客
04-03 8707
一、.NET Framework Data Provider for SQL Server 类型：.NET Framework类库 使用：System.Data.SqlClient.SqlConnection 厂商：Microsoft 标准安全连接 Data Source = myServerAddress;Initial Catalog = myDataBase;User Id = myUsername;Password = myPassword; 使用服务器名\实例名作为连接指定SQL S..
SQL Server 连接字符串构造及测试工具
04-14
本解决方案提供了一个专门用于构建和测试SQL Server连接字符串的工具。 首先，我们来了解SQL Server连接字符串的基本构成。一个标准的SQL Server连接字符串通常包含以下几个关键部分： 1. **数据源 (Data Source)*...
ASP的SQL Server连接字符串介绍
06-15
本文将详细介绍ASP环境中SQL Server连接字符串的配置方式，包括不同版本的SQL Server和不同的应用场景。 首先，连接字符串是用于指定数据库服务器位置、登录凭证以及其它连接相关的参数的一种字符串。对于ASP与SQL ...
C#开发SQL Server连接字符串构造及测试客户端软件源码.rar
最新发布
01-27
SQL Server连接字符串是用于建立C#应用与SQL Server数据库之间通信的关键元素。它包含了必要的信息，如服务器名称、数据库名、用户名和密码，以便应用程序能够成功连接到数据库。 一、SQL Server连接字符串的基本...
sqlserver连接字符串大全
11-03
### SQL Server连接字符串详解 在IT领域中，数据库的连接是进行数据操作的基础步骤之一。本文将基于“SQL Server连接字符串大全”的主题，详细介绍不同版本的SQL Server（如2000、2005等）及其不同环境下的连接字符...
Visual C++源代码 138 如何解析SQL Server连接字符串信息
06-19
Visual C++源代码 138 如何解析SQL Server连接字符串信息Visual C++源代码 138 如何解析SQL Server连接字符串信息Visual C++源代码 138 如何解析SQL Server连接字符串信息Visual C++源代码 138 如何解析SQL Server...
SQL SERVER数据库连接客户端
11-12
数据库连接软件 sqlncli2005、sqlncli2008、sqlncli2012、sqlncli_x64
C#通用数据库连接串实例，可连接Access、Excel以及Sql server 数据库
05-29
C#通用数据库连接串实例，可连接Access、Excel以及Sql server 数据库
SQL Server 连接字符串的写法
08-27 974
        Data Source=./SQLEXPRESS;Integrated Security=True;Connect Timeout=30;Password=123456;User ID=sa;DataBase=lfcars; 这是Codesmith链接字符串         ASP 中通过 OLE DB 接口方式连接 Microsoft SQL Server 2000
Web.Config和Sql Server2005连接字符串总结(转）
dnmd6272的博客
12-16 417
Web.Config和Sql Server2005连接字符串总结 收藏 转自http://blog.csdn.net/Sunboy_2050/archive/2009/12/04/4942616.aspxSQL Native Client ODBC Driver 标准安全连接 Driver={SQL Native Client};Server=myServerAddres...
SQL Server 2008 连接字符串
tianlianchao1982的专栏
09-23 2315
.NET Framework Data Provider for SQL Server 类型: .NET Framework Class Library 用法: System.Data.SqlClient.SqlConnection 制造商:  Microsoft 更
SQL Server 连接字符串的使用和属性介绍
dfg6565的博客
06-28 748
微软的SQL Server 2005和SQL Server 2000在数据库访问上面是通用的，关键在于连接字符串的配置，其实这两种数据的连接串是可以通用的，关键是数据库服务器地址的问题。SQL Server 2005和2000数据库默认访问端口不一样。2005是2317，2000的是1433。下面四个连接串都可以访问2000。 1、Server=myServer...
sqlserver connectionString
07-16 7078
1.连接字符串：data source=192.168.1.22;initial catalog=dbs_his;user id=sa;password=123456;connection timeout=5
sqlserver connection string
04-26 208
sqlserver connection string server=ip;Network=xxxxx;uid=***;pwd=***; database=db;failover partner=ip2 ...
数据库的连接字符串大全
anjujiao1678的博客
01-24 1059
一、.NET Framework Data Provider for SQL Server 类型：.NET Framework类库使用：System.Data.SqlClient.SqlConnection厂商：Microsoft 1.标准安全连接 Data Source = myServerAddress;Initial Catalog = myDataBase;User I...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值