Microsoft Access giving ASYNC_NETWORK_IO on new PC Build

Question

Background:

I've been supporting a legacy MS Access Front end with Linked Tables to SQL Server for about a year. The code is terrible, and we're re-writing as an MVC App. But for the next year or so we still have to support it.

Last week I upgraded my laptop. More RAM, bigger HHD etc ... On my old laptop, I had a copy of the SQL Express Database, and the Access, and it ran fine. I open a form in Access, and it appeared after a couple of seconds.

New laptop. Twice the RAM ... takes minutes to load the same form with the same database running locally. When I look at the SQL Server, I see the queries that the Access is calling and they're all with ASYNC_NETWORK_IO

My task manager on my PC shows memory running at 40%, and CPU at 30%. There is no network as Access and SQL are on the same PC.

Does anyone know why the Access front end would be taking minutes on my new laptop, compared to seconds on the old, to load the same form?

Thanks in advance.

question from:https://stackoverflow.com/questions/65949439/microsoft-access-giving-async-network-io-on-new-pc-build

Answer 1

Answering my own question for the next unfortunate person who has the issue.

• On my old laptop I was running SQL Express 2019
• On my new laptop I installed SQL Developer Edition 2019

Clutching at straws, I installed Express 2019 on the new laptop, changed the connection string, and it's back to working normally!

Unbelievable that using Developer Edition caused so much more heartache than Express ... would love if someone could answer that for me!