November 4, 2026 at 2:45 pm
Has anyone encountered recurring request latency when using Microsoft Access with SQL Server 2025 through ODBC Driver 18?
In several existing Access applications, a simple DAO test behaves as follows:
No forms open: approximately 0–4 ms per request after the initial execution.
Certain bound forms open: approximately 150–250 ms per request.
Closing the affected objects restores normal performance in the tested scenarios.
This affects both a two-row SELECT through a linked table and a pass-through query executing SELECT 1.
Extended Events on SQL Server 2025 measured less than 1 ms for those requests while Access measured approximately 200 ms. The test requests used the same server session.
I reproduced the behaviour on:
SQL Server 2025 Developer builds 17.0.1145.4 and 17.0.1135.8.
Access 2021 and Access 2019, both 64-bit.
Two ODBC Driver 18 installations.
Using the same laptop, Access installation and ODBC Driver 18, the test remains fast with the list form open against SQL Server 2016 and SQL Server 2022.
Important limitations: the 2016/2022 servers contain an older database copy, and those connections are remote while the laptop's SQL Server 2025 connection is local. This is therefore evidence of an environment-dependent difference, not proof of an engine defect.
ODBC tracing is disabled. Compatibility-level changes did not resolve it. Linked SQL Server views and fully fetching some recordsets improved specific cases, but did not consistently eliminate the problem.
Has anyone seen a similar pattern, or identified a relevant setting, fix, or client-side diagnostic approach? In particular, what would you capture to locate time spent outside SQL Server's recorded execution duration?
I am also arranging a Microsoft support incident and can provide the small VBA timing procedure if useful.
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply