Qlik Community

Ask a Question

Connectivity & Data Prep

Discussion board where members can learn more about Qlik Sense Data Connectivity.

Announcements
Support Cases coming to Qlik Community Oct. 4! Start chats, open cases, explore resources: READ DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
mjperreault
Creator
Creator

Qlik SQL Server much slower than OLE DB connection

Hi All,

 

Currently I have an OLE DB connection in my Qlik Sense site to a Microsoft SQL Server Database using the Microsoft OLE DB Provider for SQL Server.  Pretty soon on the database server we are going to be upgrading from TLS 1.0 to TLS 1.2 at which point in time the OLE DB connection will no longer be supported and will not work.  

https://stackoverflow.com/questions/46011694/does-microsoft-ole-db-provider-for-sql-server-support-t...

In anticipation of this I have created another Data Connection using the Microsoft SQL Server connector provided in the ODBC Connector Package.  

I have noticed significant load time impacts of using the ODBC connection, I have a query that takes roughly 3 minutes using the OLE DB connection but takes 11 minutes using the ODBC connection.  I was wondering if anyone else has seen this significant of a load discrepancy between OLE DB and ODBC and any solutions that may have.  As OLE DB is no longer going to be supported by SQL Server what are people planning on doing about it?

Thanks in advance for any thoughts or insights ! 

Mark

Labels (5)
1 Solution

Accepted Solutions
fosuzuki
Partner
Partner

This may not really answer your question, but I'd say that your understanding "As OLE DB is no longer going to be supported by SQL Server" may be is wrong. Probably you just need to use a newer OLEDB driver.

The stackoverflow thread you shared has this hint: "The new OLE DB driver, 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)."

View solution in original post

2 Replies
fosuzuki
Partner
Partner

This may not really answer your question, but I'd say that your understanding "As OLE DB is no longer going to be supported by SQL Server" may be is wrong. Probably you just need to use a newer OLEDB driver.

The stackoverflow thread you shared has this hint: "The new OLE DB driver, 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)."

View solution in original post

mjperreault
Creator
Creator
Author

Thanks @fosuzuki for your response, yes you are right my understanding was wrong! After some more reading I found the below and installed the Microsoft OLE DB Driver for SQL Server which is working.

https://docs.microsoft.com/en-us/archive/blogs/sqlnativeclient/announcing-the-new-release-of-ole-db-...