When using SQL Native Access Client SQL OLE DB, the application intent connection string should be specified Sample Connection Strings - Implementing the Application Intent connection propertyĭepending on the SNAC protocol you are using there is a slight variation in the application intent connection string property.
Under the 'Install Instructions' link, you will find an individual link for the SQL Server 2012 Native Client.
FULL CONVERT ENTERPRISE CONNECTION STRING INSTALL
Install Microsoft® SQL Server® 2012 Native Client from the Microsoft® SQL Server® 2012 Feature Pack. : The SNAC version that ships with SQL Server is. Use SQL Server 2012 Setup to install the SQL Server Client Tools. You can obtain the SQL Native Access Client with one of the following: SNAC version 11 (sqlncli11.dll) supports the Application Intent connection property. The SNAC provider must be installed where your client application runs.
You can specify the Application Intent connection property when connecting to SQL Server via SQLClient, SNAC ODBC or SNAC OLEDB. Support for read-only routing of SQL connections is via the SQL Native Access Client provider (SNAC) version 11. SQL Native Access Client Supports Application Intent property Once you have configured your SQL Server availability group for read-only routing (see blog 'End to End - Using a Listener to Connect to a Secondary Replica (Read-Only Routing)') you must install the SQL Native Access Client (SNAC) provider that supports application intent connections and you must write your application using the correct and necessary connection properties, to successfully connect to the secondary read-only replica.
0 kommentar(er)
