关闭

connectionstrings

893人阅读 评论(0) 收藏 举报
www.connectionstrings.com
#sql server 2000 
  *      ODBC


          o  Standard Security:
            "Driver={SQL Server};Server=Aron1;Database=pubs;Uid=sa;Pwd=asdasd;"


          o  Trusted connection:
            "Driver={SQL Server};Server=Aron1;Database=pubs;Trusted_Connection=yes;"


          o  Prompt for username and password:
            oConn.Properties("Prompt") = adPromptAlways
            oConn.Open "Driver={SQL Server};Server=Aron1;DataBase=pubs;"


    *  OLE DB, OleDbConnection (.NET)


          o  Standard Security:
            "Provider=sqloledb;Data Source=Aron1;Initial Catalog=pubs;User Id=sa;Password=asdasd;"


          o  Trusted Connection:
            "Provider=sqloledb;Data Source=Aron1;Initial Catalog=pubs;Integrated Security=SSPI;"

                (use serverName/instanceName as Data Source to use an specifik SQLServer instance, only SQLServer2000)

          o  Prompt for username and password:
            oConn.Provider = "sqloledb"
            oConn.Properties("Prompt") = adPromptAlways
            oConn.Open "Data Source=Aron1;Initial Catalog=pubs;"


          o  Connect via an IP address:
            "Provider=sqloledb;Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=pubs;User ID=sa;Password=asdasd;"

                (DBMSSOCN=TCP/IP instead of Named Pipes, at the end of the Data Source is the port to use (1433 is the default))

    *  SqlConnection (.NET)


          o  Standard Security:
            "Data Source=Aron1;Initial Catalog=pubs;User Id=sa;Password=asdasd;"
               - or -
            "Server=Aron1;Database=pubs;User ID=sa;Password=asdasd;Trusted_Connection=False"
               (both connection strings produces the same result)


          o  Trusted Connection:
            "Data Source=Aron1;Initial Catalog=pubs;Integrated Security=SSPI;"
               - or -
            "Server=Aron1;Database=pubs;Trusted_Connection=True;"
               (both connection strings produces the same result)

                (use serverName/instanceName as Data Source to use an specifik SQLServer instance, only SQLServer2000)

          o  Connect via an IP address:
            "Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=pubs;User ID=sa;Password=asdasd;"

                (DBMSSOCN=TCP/IP instead of Named Pipes, at the end of the Data Source is the port to use (1433 is the default))

          o  Declare the SqlConnection:

                C#:
                using System.Data.SqlClient;
                SqlConnection oSQLConn = new SqlConnection();
                oSQLConn.ConnectionString="my connection string";
                oSQLConn.Open();



                VB.NET:
                Imports System.Data.SqlClient
                Dim oSQLConn As SqlConnection = New SqlConnection()
                oSQLConn.ConnectionString="my connection string"
                oSQLConn.Open()

    *  Data Shape


          o  MS Data Shape
            "Provider=MSDataShape;Data Provider=SQLOLEDB;Data Source=Aron1;Initial Catalog=pubs;User ID=sa;Password=asdasd;"

                Want to learn data shaping? Check out 4GuyfFromRolla's great article about Data Shaping >>

    *  Read more


          o  How to define which network protocol to use

                +
                  Example:
                  "Provider=sqloledb;Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=pubs;User ID=sa;Password=asdasd;"

                  Name     Network library
                  dbnmpntw     Win32 Named Pipes
                  dbmssocn     Win32 Winsock TCP/IP
                  dbmsspxn     Win32 SPX/IPX
                  dbmsvinn     Win32 Banyan Vines
                  dbmsrpcn     Win32 Multi-Protocol (Windows RPC)


                  Important note!
                  When connecting through the SQLOLEDB provider use the syntax Network Library=dbmssocn
                  and when connecting through MSDASQL provider use the syntax Network=dbmssocn

          o  All SqlConnection connection string properties

                +
                  This table shows all connection string properties for the ADO.NET SqlConnection object. Most of the properties are also used in ADO. All properties and descriptions is from msdn.

                  Name     Default     Description
                  Application Name           The name of the application, or '.Net SqlClient Data Provider' if no application name is provided.
                  AttachDBFilename
                  -or-
                  extended properties
                  -or-
                  Initial File Name           The name of the primary file, including the full path name, of an attachable database. The database name must be specified with the keyword 'database'.
                  Connect Timeout
                  -or-
                  Connection Timeout     15     The length of time (in seconds) to wait for a connection to the server before terminating the attempt and generating an error.
                  Connection Lifetime     0     When a connection is returned to the pool, its creation time is compared with the current time, and the connection is destroyed if that time span (in seconds) exceeds the value specified by connection lifetime. Useful in clustered configurations to force load balancing between a running server and a server just brought on-line.
                  Connection Reset     'true'     Determines whether the database connection is reset when being removed from the pool. Setting to 'false' avoids making an additional server round-trip when obtaining a connection, but the programmer must be aware that the connection state is not being reset.
                  Current Language           The SQL Server Language record name.
                  Data Source
                  -or-
                  Server
                  -or-
                  Address
                  -or-
                  Addr
                  -or-
                  Network Address           The name or network address of the instance of SQL Server to which to connect.
                  Enlist     'true'     When true, the pooler automatically enlists the connection in the creation thread's current transaction context.
                  Initial Catalog
                  -or-
                  Database           The name of the database.
                  Integrated Security
                  -or-
                  Trusted_Connection     'false'     Whether the connection is to be a secure connection or not. Recognized values are 'true', 'false', and 'sspi', which is equivalent to 'true'.
                  Max Pool Size     100     The maximum number of connections allowed in the pool.
                  Min Pool Size     0     The minimum number of connections allowed in the pool.
                  Network Library
                  -or-
                  Net     'dbmssocn'     The network library used to establish a connection to an instance of SQL Server. Supported values include dbnmpntw (Named Pipes), dbmsrpcn (Multiprotocol), dbmsadsn (Apple Talk), dbmsgnet (VIA), dbmsipcn (Shared Memory) and dbmsspxn (IPX/SPX), and dbmssocn (TCP/IP).
                  The corresponding network DLL must be installed on the system to which you connect. If you do not specify a network and you use a local server (for example, "." or "(local)"), shared memory is used.
                  Packet Size     8192     Size in bytes of the network packets used to communicate with an instance of SQL Server.
                  Password
                  -or-
                  Pwd           The password for the SQL Server account logging on.
                  Persist Security Info     'false'     When set to 'false', security-sensitive information, such as the password, is not returned as part of the connection if the connection is open or has ever been in an open state. Resetting the connection string resets all connection string values including the password.
                  Pooling     'true'     When true, the SQLConnection object is drawn from the appropriate pool, or if necessary, is created and added to the appropriate pool.
                  User ID           The SQL Server login account.
                  Workstation ID     the local computer name     The name of the workstation connecting to SQL Server.


                  Note
                  Use ; to separate each property.
                  If a name occurs more than once, the value from the last one in the connection string will be used.
                  If you are building your connection string in your app using values from user input fields, make sure the user can't change the connection string by inserting an additional property with another value within the user value.

#  SQL Server 2005

    *  SQL Native Client ODBC Driver


          o  Standard security:
            "Driver={SQL Native Client};Server=Aron1;Database=pubs;UID=sa;PWD=asdasd;"


          o  Trusted connection:
            "Driver={SQL Native Client};Server=Aron1;Database=pubs;Trusted_Connection=yes;"

                Equivalents
                Integrated Security=SSPI equals Trusted_Connection=yes

          o  Prompt for username and password:
            oConn.Properties("Prompt") = adPromptAlways
            oConn.Open "Driver={SQL Native Client};Server=Aron1;DataBase=pubs;"


          o  Enabling MARS (multiple active result sets):
            "Driver={SQL Native Client};Server=Aron1;Database=pubs;Trusted_Connection=yes;MARS_Connection=yes"

                Equivalents
                MultipleActiveResultSets=true equals MARS_Connection=yes

                Using MARS with SQL Native Client, by Chris Lee >>

          o  Encrypt data sent over network:
            "Driver={SQL Native Client};Server=Aron1;Database=pubs;Trusted_Connection=yes;Encrypt=yes"


          o  Attach a database file on connect to a local SQL Server Express instance:
            "Driver={SQL Native Client};Server=./SQLExpress;AttachDbFilename=c:/asd/qwe/mydbfile.mdf;Database=dbname;Trusted_Connection=Yes;"
               - or -
            "Driver={SQL Native Client};Server=./SQLExpress;AttachDbFilename=|DataDirectory|mydbfile.mdf;Database=dbname;Trusted_Connection=Yes;"
               (use |DataDirectory| when your database file resides in the data directory)

                Why is the "Database" parameter needed? Answer: If the database was previously 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)

                Using SQL Server 2005 Express? Don't miss the server name syntax: SERVERNAME/SQLEXPRESS (Substitute "SERVERNAME" with the name of the computer)

    *  SQL Native Client OLE DB Provider


          o  Standard security:
            "Provider=SQLNCLI;Server=Aron1;Database=pubs;UID=sa;PWD=asdasd;"


          o  Trusted connection:
            "Provider=SQLNCLI;Server=Aron1;Database=pubs;Trusted_Connection=yes;"

                Equivalents
                Integrated Security=SSPI equals Trusted_Connection=yes

          o  Prompt for username and password:
            oConn.Properties("Prompt") = adPromptAlways
            oConn.Open "Provider=SQLNCLI;Server=Aron1;DataBase=pubs;"


          o  Enabling MARS (multiple active result sets):
            "Provider=SQLNCLI;Server=Aron1;Database=pubs;Trusted_Connection=yes;MarsConn=yes"

                Equivalents
                MarsConn=yes equals MultipleActiveResultSets=true equals MARS_Connection=yes

                Using MARS with SQL Native Client, by Chris Lee >>

          o  Encrypt data sent over network:
            "Provider=SQLNCLI;Server=Aron1;Database=pubs;Trusted_Connection=yes;Encrypt=yes"


          o  Attach a database file on connect to a local SQL Server Express instance:
            "Provider=SQLNCLI;Server=./SQLExpress;AttachDbFilename=c:/asd/qwe/mydbfile.mdf;Database=dbname;Trusted_Connection=Yes;"
               - or -
            "Provider=SQLNCLI;Server=./SQLExpress;AttachDbFilename=|DataDirectory|mydbfile.mdf;Database=dbname;Trusted_Connection=Yes;"
               (use |DataDirectory| when your database file resides in the data directory)

                Why is the "Database" parameter needed? Answer: If the database was previously 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)

                Using SQL Server 2005 Express? Don't miss the server name syntax: SERVERNAME/SQLEXPRESS (Substitute "SERVERNAME" with the name of the computer)

    *  SqlConnection (.NET)


          o  Standard Security:
            "Data Source=Aron1;Initial Catalog=pubs;User Id=sa;Password=asdasd;"
               - or -
            "Server=Aron1;Database=pubs;User ID=sa;Password=asdasd;Trusted_Connection=False"
               (both connection strings produces the same result)


          o  Trusted Connection:
            "Data Source=Aron1;Initial Catalog=pubs;Integrated Security=SSPI;"
               - or -
            "Server=Aron1;Database=pubs;Trusted_Connection=True;"
               (both connection strings produces the same result)

                (use serverName/instanceName as Data Source to use an specifik SQLServer instance)

          o  Connect via an IP address:
            "Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=pubs;User ID=sa;Password=asdasd;"

                (DBMSSOCN=TCP/IP instead of Named Pipes, at the end of the Data Source is the port to use (1433 is the default))

          o  Enabling MARS (multiple active result sets):
            "Server=Aron1;Database=pubs;Trusted_Connection=True;MultipleActiveResultSets=true"

                Note! 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 >>

          o  Attach a database file on connect to a local SQL Server Express instance:
            "Server=./SQLExpress;AttachDbFilename=c:/asd/qwe/mydbfile.mdf;Database=dbname;Database=dbname;Trusted_Connection=Yes;"
               - or -
            "Server=./SQLExpress;AttachDbFilename=|DataDirectory|mydbfile.mdf;Database=dbname;Trusted_Connection=Yes;"
               (use |DataDirectory| when your database file resides in the data directory)

                Why is the "Database" parameter needed? Answer: If the database was previously attached, SQL Server does not reattach it (it uses the attached database as the default for the connection).

          o  Using "User Instance" on a local SQL Server Express instance:
            "Data Source=./SQLExpress;integrated security=true;attachdbfilename=|DataDirectory|/mydb.mdf;user instance=true;"

                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. To enable the functionality: sp_configure 'user instances enabled','1' (0 to disable)

                Using SQL Server 2005 Express? Don't miss the server name syntax: SERVERNAME/SQLEXPRESS (Substitute "SERVERNAME" with the name of the computer)

    *  Context Connection - connecting to "self" from within your CLR stored prodedure/function


          o  C#:
            using(SqlConnection connection = new SqlConnection("context connection=true"))
            {
                connection.Open();
                // Use the connection
            }


          o  Visual Basic:
            Using connection as new SqlConnection("context connection=true")
                connection.Open()
                ' Use the connection
            End Using


                The context connection lets you execute Transact-SQL statements in the same context (connection) that your code was invoked in the first place.

    *  Read more


          o  When to use SQL Native Client?

                +  .Net applications
                  Do not use the SQL Native Client. Use the .NET Framework Data Provider for SQL Server (SqlConnection).
                +  COM applications, all other then .Net applications
                  Use the SQL Native Client if you are accessing an SQL Server 2005 and need the new features of SQL Server 2005 such as MARS, encryption, XML data type etc. Continue use your current provider (OLE DB / ODBC through the MDAC package) if you are not connecting to an SQL Server 2005 (that's quite obvious eh..) or if you are connecting to an SQL Server 2005 but are not using any of the new SQL Server 2005 features.

                      For more details on the differences between MDAC and SQL Native Client, read this msdn article >>

#  Access

    *  ODBC


          o  Standard Security:
            "Driver={Microsoft Access Driver (*.mdb)};Dbq=C:/mydatabase.mdb;Uid=Admin;Pwd=;"


          o  Workgroup:
            "Driver={Microsoft Access Driver (*.mdb)};Dbq=C:/mydatabase.mdb;SystemDB=C:/mydatabase.mdw;"


          o  Exclusive:
            "Driver={Microsoft Access Driver (*.mdb)};Dbq=C:/mydatabase.mdb;Exclusive=1;Uid=admin;Pwd="


    *  OLE DB, OleDbConnection (.NET)


          o  Standard security:
            "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=/somepath/mydb.mdb;User Id=admin;Password=;"


          o  Workgroup (system database):
            "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=/somepath/mydb.mdb;Jet OLEDB:System Database=system.mdw;"


          o  With password:
            "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=/somepath/mydb.mdb;Jet OLEDB:Database Password=MyDbPassword;"


#  Oracle

    *  ODBC


          o  New version:
            "Driver={Microsoft ODBC for Oracle};Server=OracleServer.world;Uid=Username;Pwd=asdasd;"


          o  Old version:
            "Driver={Microsoft ODBC Driver for Oracle};ConnectString=OracleServer.world;Uid=myUsername;Pwd=myPassword;"


    *  OLE DB, OleDbConnection (.NET)


          o  Standard security:
            "Provider=msdaora;Data Source=MyOracleDB;User Id=UserName;Password=asdasd;"

                This one's from Microsoft, the following are from Oracle

          o  Standard Security:
            "Provider=OraOLEDB.Oracle;Data Source=MyOracleDB;User Id=Username;Password=asdasd;"


          o  Trusted Connection:
            "Provider=OraOLEDB.Oracle;Data Source=MyOracleDB;OSAuthent=1;"


    *  OracleConnection (.NET)


          o  Standard:
            "Data Source=MyOracleDB;Integrated Security=yes;"

                This one works only with Oracle 8i release 3 or later

          o  Specifying username and password:
            "Data Source=MyOracleDB;User Id=username;Password=passwd;Integrated Security=no;"

                This one works only with Oracle 8i release 3 or later

          o  Declare the OracleConnection:

                C#:
                using System.Data.OracleClient;
                OracleConnection oOracleConn = new OracleConnection();
                oOracleConn.ConnectionString = "my connection string";
                oOracleConn.Open();



                VB.NET:
                Imports System.Data.OracleClient
                Dim oOracleConn As OracleConnection = New OracleConnection()
                oOracleConn.ConnectionString = "my connection string"
                oOracleConn.Open()

                Missing the System.Data.OracleClient namespace? Download .NET Managed Provider for Oracle >>

                Great article! "Features of Oracle Data Provider for .NET" by Rama Mohan G. at C# Corner

    *  Core Labs OraDirect (.NET)


          o  Standard:
            "User ID=scott; Password=tiger; Host=ora; Pooling=true; Min Pool Size=0;Max Pool Size=100; Connection Lifetime=0"

                Read more at Core Lab and the product page.

    *  Data Shape


          o  MS Data Shape:
            "Provider=MSDataShape.1;Persist Security Info=False;Data Provider=MSDAORA;Data Source=orac;user id=username;password=mypw"

                Want to learn data shaping? Check out 4GuyfFromRolla's great article about Data Shaping >>

#  MySQL

    *  MyODBC


          o  MyODBC 2.50 Local database:
            "Driver={mySQL};Server=localhost;Option=16834;Database=mydatabase;"


          o  MyODBC 2.50 Remote database:
            "Driver={mySQL};Server=data.domain.com;Port=3306;Option=131072;Stmt=;Database=my-database;Uid=username;Pwd=password;"


          o  MyODBC 3.51 Local database:
            "DRIVER={MySQL ODBC 3.51 Driver};SERVER=localhost;DATABASE=myDatabase;USER=myUsername;PASSWORD=myPassword;OPTION=3;"


          o  MyODBC 3.51 Remote database:
            "DRIVER={MySQL ODBC 3.51 Driver};SERVER=data.domain.com;PORT=3306;DATABASE=myDatabase; USER=myUsername;PASSWORD=myPassword;OPTION=3;"


    *  OLE DB, OleDbConnection (.NET)


          o  Standard:
            "Provider=MySQLProv;Data Source=mydb;User Id=UserName;Password=asdasd;"
    *  Connector/Net 1.0 (.NET)


          o  Standard:
            "Server=Server;Database=Test;Uid=UserName;Pwd=asdasd;"

                Download the driver at MySQL Developer Zone.

          o  Specifying port:
            "Server=Server;Port=1234;Database=Test;Uid=UserName;Pwd=asdasd;"

                Default port is 3306. Enter value -1 to use a named pipe connection.

          o  Declare the MySqlClient connection:

                C#:
                using MySql.Data.MySqlClient;
                MySqlConnection oMySqlConn = new MySqlConnection();
                oMySqlConn.ConnectionString = "Server=Server;Database=Test;Uid=UserName;Pwd=asdasd;";
                oMySqlConn.Open();



                VB.NET:
                Imports MySql.Data.MySqlClient
                Dim oMySqlConn As MySqlConnection = New MySqlConnection()
                oMySqlConn.ConnectionString = "Server=Server;Database=Test;Uid=UserName;Pwd=asdasd;"
                oMySqlConn.Open()

    *  MySqlConnection (.NET)


          o  eInfoDesigns.dbProvider:
            "Data Source=server;Database=mydb;User ID=username;Password=pwd;Command Logging=false"

                This one is used with eInfoDesigns dbProvider, an add-on to .NET

          o  Declare the MySqlConnection:

                C#:
                using eInfoDesigns.dbProvider.MySqlClient;
                MySqlConnection oMySqlConn = new MySqlConnection();
                oMySqlConn.ConnectionString = "my connection string";
                oMySqlConn.Open();



                VB.NET:
                Imports eInfoDesigns.dbProvider.MySqlClient
                Dim oMySqlConn As MySqlConnection = New MySqlConnection()
                oMySqlConn.ConnectionString = "my connection string"
                oMySqlConn.Open()

    *  SevenObjects MySqlClient (.NET)


          o  Standard:
            "Host=server; UserName=myusername; Password=mypassword;Database=mydb;"

                This is a freeware ADO.Net data provider from SevenObjects

    *  Core Labs MySQLDirect (.NET)


          o  Standard:
            "User ID=root; Password=pwd; Host=localhost; Port=3306; Database=test;Direct=true; Protocol=TCP; Compress=false; Pooling=true; Min Pool Size=0;Max Pool Size=100; Connection Lifetime=0"

                Read more at Core Lab and the product page.

#  Interbase
0
0

查看评论
* 以上用户言论只代表其个人观点,不代表CSDN网站的观点或立场
    个人资料
    • 访问:4638次
    • 积分:82
    • 等级:
    • 排名:千里之外
    • 原创:3篇
    • 转载:1篇
    • 译文:0篇
    • 评论:0条
    文章存档