Contents
Can you use msoledb to establish a linked server?
Establishing a Linked Server to SQL Server using the MSOLEDB driver is supported on following version of SQL Server: All other versions of SQL Server except those listed above will result in the following error when using the MSOLEDB driver for establishing linked server.
How to establish a linked server with SQL Server?
This particular blog will discuss how to leverage the new MSOLEDB driver to establish linked server with SQL Server. The MSOLEDB driver is the latest OLEDB Driver from Microsoft. It supports TLS 1.2 along with connection string attributes like MultiSubnetFailover.
Why are linked servers connecting to a multi subnet failover cluster?
This appears to be due to the linked server connection talking to a multi subnet failover cluster (as described here) Other than following the solution of implementing an ODBC connection on each node of our publisher (also a multi subnet failover cluster) is there anything else we can try to fix linked servers connecting to a multi subnet FCI?
Why is multisubnetfailover = true in the connection string?
The listener has two IP addresses because it spans subnets so we are specifying Multisubnetfailover=true in our connection string. When attempting to make a connection to the listener I get the following error:
How to configure OLE DB on SQL Server?
Right-click on Linked Servers and select New Linked Server. 4. Give your new Linked Server a title in the Linked server: text box. 5. For the Server type, select Other data source and select the desired IBM OLE DB data provider.
Which is Ms OLEDB provider for SQL Server 2017?
Microsoft Distributed Transaction Coordinator (MS DTC) has stopped this transaction. By default, SQL Server 2017 and earlier versions use the Microsoft OLEDB Provider for SQL Server when establishing linked server connections.