Download Ole Db Driver for Sql Server

Question

You seem to have washed everything right. Still the link you posted has a annotate on the page which states:

This page is no longer maintained. Please read the details below.

If y’all open the details tab by clicking the
+
sign you will be greeted with the post-obit information:

This page is no longer maintained. To download the Microsoft OLE DB Commuter 18 for SQL Server, delight go to the documentation page at
https://aka.ms/downloadmsoledbsql.

_{This volition take you to

https://docs.microsoft.com/en-gb/sql/connect/oledb/download-oledb-driver-for-sql-server?view=sql-server-ver15

(Merely in case the curt link becomes obsolete.)}

I would grab the newest OLE DB drivers from there.

Microsoft OLE DB Driver for SQL Server

Take your fourth dimension and read the information about the
Unlike generations of OLE DB Drivers
on the web page. In the sub department titled
iii. Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL)
there is this minor note that states:

The new OLE DB provider is called the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL). The new provider will be updated with the most recent server features going forrard.

Based on what yous wrote in your question, you lot must be using the correct OLE DB driver. Good….

Create Linked Server from SQL Server 2019 to SQL Server 2016

I have multiple instances on my laptop and created a linked server from my 2019 instance to a SQL Server 2016 case using the post-obit stored procedures:

        Apply [chief] GO EXEC chief.dbo.sp_addlinkedserver      @server = N'MSOLEDBDSQL',      @srvproduct=N'SERVER\sql2016',      @provider=N'MSOLEDBSQL',      @datasrc=N'SERVER\sql2016',      @itemize=N'chief'  Become EXEC main.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=N'collation uniform', @optvalue=N'faux' Go EXEC chief.dbo.sp_serveroption @server=Due north'MSOLEDBDSQL', @optname=N'data admission', @optvalue=North'true' Go EXEC master.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=N'dist', @optvalue=Northward'false' GO EXEC principal.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=Northward'pub', @optvalue=North'false' GO EXEC main.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=N'rpc', @optvalue=N'imitation' GO EXEC master.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=N'rpc out', @optvalue=North'false' GO EXEC master.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=North'sub', @optvalue=N'faux' GO EXEC master.dbo.sp_serveroption @server=North'MSOLEDBDSQL', @optname=Due north'connect timeout', @optvalue=N'0' Become EXEC master.dbo.sp_serveroption @server=Northward'MSOLEDBDSQL', @optname=Due north'collation name', @optvalue=zippo GO EXEC master.dbo.sp_serveroption @server=North'MSOLEDBDSQL', @optname=N'lazy schema validation', @optvalue=Due north'false' GO EXEC master.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=North'query timeout', @optvalue=N'0' Go EXEC chief.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=N'utilize remote collation', @optvalue=N'truthful' Become EXEC chief.dbo.sp_serveroption @server=Northward'MSOLEDBDSQL', @optname=N'remote proc transaction promotion', @optvalue=N'true' Get Employ [chief] GO EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname = Due north'MSOLEDBDSQL', @locallogin = NULL , @useself = N'True' Become

I then queried the linked server with the following statement:

        SELECT name, create_date FROM MSOLEDBDSQL.chief.sys.databases

Which promptly returned:

          +----------------------+-------------------------+ |         name         |       create_date       | +----------------------+-------------------------+ | master               | 2003-04-08 09:thirteen:36.390 | | tempdb               | 2020-11-03 16:29:26.787 | | model                | 2003-04-08 09:13:36.390 | | msdb                 | 2016-04-30 00:46:38.773 | | SSODB                | 2020-01-03 14:35:34.143 | | BizTalkMgmtDb        | 2020-01-03 xiv:35:39.570 | | BizTalkDTADb         | 2020-01-03 14:35:43.370 | | BizTalkMsgBoxDb      | 2020-01-03 14:35:45.137 | | BizTalkRuleEngineDb  | 2020-01-03 14:36:21.603 | | BAMPrimaryImport     | 2020-01-03 fourteen:36:34.713 | | BAMArchive           | 2020-01-03 fourteen:36:35.333 | | DemoDB               | 2020-01-15 12:04:41.427 | | BAMAlertsApplication | 2020-01-28 14:40:twenty.767 | +----------------------+-------------------------+

Seems to work just fine.

Read: Ch340 Driver Windows 10 64 Bit Download

Create Linked Server from SQL Server 2016 (CI) instance to SQL Server 2016 case

I then created a linked server from my 2016 Case-insensitive instance to the same SQL Server 2016 instance using the following stored procedures:

        Utilise [main] Go EXEC principal.dbo.sp_addlinkedserver      @server = North'MSOLEDBDSQL',      @srvproduct=North'SERVER\sql2016',      @provider=N'MSOLEDBSQL',      @datasrc=Due north'SERVER\sql2016',      @catalog=N'master'  Get EXEC main.dbo.sp_serveroption @server=Northward'MSOLEDBDSQL', @optname=N'collation compatible', @optvalue=N'false' Get EXEC master.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=Due north'data access', @optvalue=Northward'true' Go EXEC master.dbo.sp_serveroption @server=Northward'MSOLEDBDSQL', @optname=Northward'dist', @optvalue=N'false' Go EXEC chief.dbo.sp_serveroption @server=Due north'MSOLEDBDSQL', @optname=N'pub', @optvalue=N'false' Go EXEC primary.dbo.sp_serveroption @server=North'MSOLEDBDSQL', @optname=Due north'rpc', @optvalue=N'imitation' Get EXEC chief.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=N'rpc out', @optvalue=N'false' Become EXEC master.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=N'sub', @optvalue=N'imitation' Become EXEC principal.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=N'connect timeout', @optvalue=N'0' Go EXEC main.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=Northward'collation name', @optvalue=null GO EXEC main.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=N'lazy schema validation', @optvalue=Northward'false' Go EXEC master.dbo.sp_serveroption @server=North'MSOLEDBDSQL', @optname=N'query timeout', @optvalue=N'0' GO EXEC master.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=Due north'utilise remote collation', @optvalue=N'true' Become EXEC master.dbo.sp_serveroption @server=N'MSOLEDBDSQL', @optname=N'remote proc transaction promotion', @optvalue=North'true' Get Apply [chief] Become EXEC chief.dbo.sp_addlinkedsrvlogin @rmtsrvname = Northward'MSOLEDBDSQL', @locallogin = NULL , @useself = Due north'True' Go

I and so queried the linked server in my CI case with the post-obit statement:

        SELECT proper name, create_date FROM MSOLEDBDSQL.chief.sys.databases

Which promptly returned:

          Msg 7430, Level xvi, State three, Line i Out-of-process apply of OLE DB provider "MSOLEDBSQL" with SQL Server is not supported.  Completion time: 2020-11-05T13:41:43.0333451+01:00

This seems to correlate with what yous are observing….. Hmmm. Let’southward think this over.

Possible Causes

Collation has to be the same: CI or CS
Drivers aren’t fully 2016 compatible when connecting from a 2016 to a 2016 instance.
Something is different on SQL Server 2019 instance compared to SQL Server 2016 instance.

Read: Download Driver Amd Radeon Tm R5 Graphics

Let’southward get and have a look at the …

Ojbect Explorer | Server Objects | Linked Servers | Providers | MSOLEDBSQL Backdrop

We’ll open up the properties of the driver on the SQL Server 2019 instance I used offset:

…and the backdrop of the driver on the SQL Server 2016 CI I used in my second test:

And there we have it. The holding
Allow inprocess
on the SQL Server 2016 CI configured instance isn’t ticked. The SQL Server 2019 instance has this setting ticked. Permit’south modify it for our SQL Server 2016 instance and run the query. It works!

Solution

Ensure the selection
Allow inprocess
is ticked for the
Microsoft OLE DB Driver for SQL Server
in its properties in the
Linked Server | Providers.