Announcement: Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) Released RRS feed

  • General discussion

  • A new OLE DB driver, Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL), has been released. This new driver includes the support for the latest TLS 1.2 standards and is backwards compatible with SQL Server Native Client 11 (SQLNCLI11).

    Download: https://www.microsoft.com/en-us/download/details.aspx?id=56730

    Microsoft SQLNCLi team blog announcement: https://blogs.msdn.microsoft.com/sqlnativeclient/2018/03/30/released-microsoft-ole-db-driver-for-sql-server/

    Dan Guzman, Data Platform MVP, http://www.dbdelta.com

    Friday, March 30, 2018 11:17 PM

All replies

  • That was much needed lot of issues related to TLS was there



    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles


    Saturday, March 31, 2018 5:28 AM
  • How can we get new OLE DB driver, Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL), installed on Nanoserver?
    Wednesday, August 1, 2018 7:20 PM
  • Awesome

    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

    Wednesday, August 1, 2018 7:58 PM
  • Hi Dan,

    Can you help me understand the difference between the MSOLEDBSQL and MSODBCSQL drivers?

    If we have customers on SQL Server 2012 that we want to migrate to SQL Server 2016 (on Windows 2016 configured to only use TLS 1.2), should we install both the latest MSOLEDBSQL and MSODBC SQL drivers? We've got some apps connecting using UDL files, some using SQL Native Client 11, and others with the driver defined in connection strings.

    Just trying to determine what the "easiest" and most appropriate long-term solution would be.


    Monday, November 26, 2018 5:47 PM
  • I assume that with MSODBCSQL, you mean the ODBC SQL Server driver. The difference between the two is one is for the OLE DB interface and one is for ODBC. That is, they are by no means interchangeable. If the application is written to use ODBC, it should use the ODBC driver. If it is written to use OLE DB, it should use the OLE DB driver.

    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Monday, November 26, 2018 10:12 PM
  • You mention UDL files so that implies OLE DB. Those apps should use the latest MSOLEDBSQL driver for the long term. In the case of ADO classic, DataTypeCompatibility=80 should be included in the connection string since ADO is unaware of data types introduced after SQL Server 2000.

    I'm not exactly sure what MSODBCSQL is in this context. There is a similarly named package with an ODBC driver for Linux and macOS but it seems you are in the Windows world. Do you perhaps mean MSDASQL (the Microsoft OLE DB provider for ODBC Drivers)? It would help if you post connection string examples with the Provider or Driver specification for clarification. 

    Although it is possible for ADO apps to access SQL Server with an ODBC driver by going through the extra MSDASQL layer (e.g. "Provider=MSDASQL;Driver={SQL Server}", it would be better to use MSOLEDBSQL in that case (e.g. "Provider=MSOLEDBSQL;DataTypeCompatibility=80") since ADO is natively uses OLE DB rather than ODBC.

    Dan Guzman, Data Platform MVP, http://www.dbdelta.com

    Tuesday, November 27, 2018 3:49 AM
  • Hi Dan,

    I'm installing 64 bit version of it now (as it didn't let me install 86 version). Question - can I use this driver from Visual FoxPro (which is 32 bit application)?

    Also, this driver is not supposed to appear when I open ODBC, right? How exactly can I test connection using this driver?


    For every expert, there is an equal and opposite expert. - Becker's Law

    My blog

    My TechNet articles

    • Edited by Naomi N Tuesday, November 27, 2018 4:10 AM
    Tuesday, November 27, 2018 3:59 AM
  • Hi Dan,

    One more question - which one is the latest OleDB I just installed - how can I figure this out?

    See this picture (I'm trying to create a connection using udl)

    For every expert, there is an equal and opposite expert. - Becker's Law

    My blog

    My TechNet articles

    Tuesday, November 27, 2018 4:17 AM
  • You want the one called "Driver". The one with "Provider" is the old and antique one.

    I seem to recall that the 64-bit installation, gives you both the 32-bit and 64-bit driver.

    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Tuesday, November 27, 2018 8:08 AM