This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 32%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDW%3C/text%3E%3C/svg%3E)
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.
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 26%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYK%3C/text%3E%3C/svg%3E)
Native Client as well as SQLOLEDB are both deprecated. It is time to start using Microsoft OLEDB Driver (MSOLEDBSQL). It is available since 2018.
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.
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
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.
' 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.
Hi @Darwin Weyh,
You may use SQL Server Profiler to create and manage traces and analyze and replay trace results.
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
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:
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.