This has been going on. At first MS said they will not support TLS1.2 for OLEDB then they said, they will. You can read about it here, where they said, the support comes in March 2018

Now it looks like package has arrived. I installed it. Then I ran soft without change to connection string using old style Provider=sqloledb. That was expected to fail and it did. I changed to new style Provider=MSOLEDBSQL (see first link). And now I get

"The 'MSOLEDBSQL' provider is not registered on the local machine."

Ok. I didn't install provider after all. But I can't find it either. I thought, may be this is part of Native Client update. But that came out Jan 2018. I installed it, it didn't break anything, it didn't fix anything. Then I came across this provider that was just released. Installed it. This seem to be new ODBC version.

Bottom line, where do I get MSOLEDBSQL? Thank you

  • The new driver hasn't been released yet. It's still March.
    – Dan Guzman
    Mar 29, 2018 at 17:21

1 Answer 1


The new OLE DB driver, MSOLEDBSQL, was released today. This new driver includes the support for the latest TLS 1.2 standards and is backwards compatible with SQL Server Native Client 11 (SQLNCLI11). See the Microsoft SQLNCLi team blog announcement.

  • An interesting question. The oledb driver we use now also supports legacy Oracle connectivity. Is this new driver fully supports that? I mean, I can unit test that.... anything off your hand?
    – T.S.
    Mar 30, 2018 at 23:31
  • @T.S., MSOLEDBSQL is only for Microsoft SQL Server connectivity. Are you saying you have a single third party OLE DB driver that supports connectivity to both Microsoft SQL Server and Oracle? I wasn't aware one existed.
    – Dan Guzman
    Mar 30, 2018 at 23:46
  • It is not third party. This is microsoft's own oledb provider that we use. Of course, I might confusing here. We use OleDbDataReader, OleDbConnection, etc. Which, of course connects using different drivers because connection string is declared differently for each DB. Never mind. This is me. You're right. This is sql server driver, oracle uses old one. On the good news, we started moving to native client while ago and now we're making a push to eliminate oledb. But we still have legacy components in the field that want TLS 1.2. Currently ap uses no less than 4 providers. Thank you
    – T.S.
    Mar 31, 2018 at 1:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.