sql server connection string 2012 remote server

SQL Server can store messages for multiple languages in sysmessages. Name of an existing ODBC file data source. An empty string causes SQL Server Native Client to use the default, driver-generated SPN. Name of the failover partner server to be used if a connection cannot be made to the primary server. This keyword is deprecated, and its setting is ignored by the SQL Server Native Client ODBC driver. Specifies whether data should be encrypted before sending it over the network. This keyword overrides any values that might be specified in the Server, Network, and Address keywords. Name of an existing ODBC user or system data source. The Server keyword is required if Driver is specified and DriverCompletion is set to SQL_DRIVER_NOPROMPT.įor more information about driver names, see Using the SQL Server Native Client Header and Library Files. ODBC applications use connection strings as a parameters to the SQLDriverConnect and SQLBrowseConnect functions.Ĭonnection strings used by ODBC have the following syntax:Ĭonnection-string ::= empty-string | attribute | attribute connection-stringĪttribute ::= attribute-keyword=['. The following sections describe the keywords that can be used with the SQL Server Native Client OLE DB provider, the SQL Server Native Client ODBC driver, and ActiveX Data Objects (ADO) when using SQL Server Native Client as the data provider. It is good practice when modifying applications to use SQL Server Native Client to eliminate any dependency on connection string ambiguity. SQL Server Native Client allows ambiguity in connection strings to maintain backward compatibility (for example, some keywords may be specified more than once, and conflicting keywords may be allowed with resolution based on position or precedence).

Sql server connection string 2012 remote server