ODBC Native Client 10 Performance Issues After Windows 11 Update

Darwin Weyh 0

A legacy application using ODBC Native Client 10 has encountered significant performance issues following the latest Windows 11 update. The application previously worked well, but now it is unacceptably slow. The environment includes an in-house MSSQL 2019 Production Server. Most machines are unaffected; however, the boss, after updating to the latest non-preview version of Windows 11, has experienced this slowdown. A similar issue was noted on a development machine, which was resolved by changing the connection profile to "SQLOLEDB" — this fix did not work for the boss's machine, despite similar Dell hardware on both systems.

Also, I have a duplicate of the SQL Server dataset on my development machine which can be accessed with no delay with all drivers.

SQL Server Management Studio works all machines with no delay.

Yitzhak Khabinsky 26,386 Reputation points

2025-02-10T20:22:46.03+00:00

Native Client as well as SQLOLEDB are both deprecated. It is time to start using Microsoft OLEDB Driver (MSOLEDBSQL). It is available since 2018.
Erland Sommarskog 117.3K Reputation points MVP

2025-02-10T22:07:43.8133333+00:00

Your message is confusing. You first talk about ODBC, and then you throw in an OLE DB provider. What is your application actually using?

As Yithzak says, you should be using MSOLEDBSQL or MSOLEDBSQL19. Or ODBC 17 SQL Server Driver or ODBC 18 SQL Server Driver.

Usually, slowness is not caused by the driver, but by slow queries. The exception would be if you are using ODBC and have enabled tracing.
Darwin Weyh 0 Reputation points

2025-02-10T23:14:02.84+00:00
This is code in VB6 but has been working for 20 years. The difference between the ODBC and an OLE DB confuses me. The code that just broke was using db.Provider = "SQLNCLI10"

Here's my connection code:

Public db As New ADODB.Connection

' db.Provider = "MSOLEDBSQL19" 'tested no success

' db.Provider = "MSOLEDBSQL" 'tested no success

' db.Provider = "SQLNCLI10" ' Original works on most machines

db.Provider = "SQLOLEDB" ' Works well on one WIN 11 machine. db.Properties("Data Source").Value = "sqlserver" db.Properties("Initial Catalog").Value = "xx" db.Properties("User ID").Value = "sa" db.Properties("Password").Value = "xx" db.CommandTimeout = 60 db.Open
Darwin Weyh 0 Reputation points

2025-02-11T14:39:45.6433333+00:00

OK so mucking around somemore I replaced all the Provider and Properties with db.ConnectionString = "Driver={ODBC Driver 18 for SQL Server};Server=xx;Database=OMS;UID=sa;PWD=xx;TrustServerCertificate=YES;MARS_Connection=Yes;"

I use the same string for each server except fot the Server and from one server I get empty strings on varchar(MAX) column selects and on the other local server works as expected. So I'm believing there is a configuration error on my server. Both SQL servers are running the same version 15.0.2130.3.
Erland Sommarskog 117.3K Reputation points MVP

2025-02-11T22:11:13.4033333+00:00

' db.Provider = "MSOLEDBSQL19" 'tested no success ' db.Provider = "MSOLEDBSQL" 'tested no success

I should have mentioned that you actually need to install these providers. They don't come with the OS.

db.ConnectionString = "Driver={ODBC Driver 18 for SQL Server};Server=xx;Database=OMS;UID=sa;PWD=xx;TrustServerCertificate=YES;MARS_Connection=Yes;"

Do you really need MARS? Else take that part out. MARS can be a real go-slower button for large result sets when there is some network latency, for instance when you have the database in the cloud.

2 answers

Bruce (SqlWork.com) 71,591 Reputation points

2025-02-10T23:40:49.7433333+00:00

vb6 is 32 bit only (and out of support as are all its adodb drivers). windows 11 is 64 bit only. windows 11 will run a 32 bit via the compatibility feature, but will not guarantee its reliable. so you are in a completely unsupported mode.

be sure the 32 bit adodb drivers where installed. see this thread about picking drivers:

https://stackoverflow.com/questions/30510857/what-provider-should-i-choose-for-my-vb6-adodb-connection-to-sql-server-2014

note: you will probably continue to have issues with windows 11 running vb6. it is probably time to upgrade the app, as windows 10 support ends 10/15/2025.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
ZoeHui-MSFT 40,896 Reputation points

2025-02-11T03:07:28.9966667+00:00

Hi @Darwin Weyh,

You may use SQL Server Profiler to create and manage traces and analyze and replay trace results.
Please sign in to rate this answer.
Darwin Weyh 0 Reputation points

2025-02-11T14:40:22.09+00:00

OK so mucking around somemore I replaced all the Provider and Properties with db.ConnectionString = "Driver={ODBC Driver 18 for SQL Server};Server=xx;Database=OMS;UID=sa;PWD=xx;TrustServerCertificate=YES;MARS_Connection=Yes;"

I use the same string for each server except fot the Server and from one server I get empty strings on varchar(MAX) column selects and on the other local server works as expected. So I'm believing there is a configuration error on my server. Both SQL servers are running the same version 15.0.2130.3.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

ODBC Native Client 10 Performance Issues After Windows 11 Update

2 answers

Your answer