Forum Discussion
Feb 2024 updates: Access->SQL Server performance issues in the Monthly Enterprise Channel
Hi,
Microsoft fixed the problem last night. There's no new build. You just have to restart Access to restore normal performance with the "SQL Server" driver.
I have also updated our documenting blog article. As written there, it would be good if affected users could briefly report back whether the fix works for them.
HeinziAT Extremely bad luck with this unusual order of appearance of the bug. S*** happens. At least you contributed to a quicker fix by reporting it here.
Servus
Karl
****************
Access Forever
Access News
Access DevCon
Access-Entwickler-Konferenz AEK
Hi Heinzi,
In January, there was a similar problem with version 2312 in the Current channel, which I only mentioned briefly as a note in the Status section of this article as it was quickly cured by Microsoft with a Feature gate.
I'll try to clarify if this is related.
Servus
Karl
****************
Access Forever
Access News
Access DevCon
Access-Entwickler-Konferenz AEK
Thanks for the reminder! It's only been a month and I already forgot about the Jan 2024 issue.
I just tried the old repro instructions we had for the Jan 2024 issue, and - voilà - that issue can be reproduced in the Feb 2024 Monthly Enterprise Build. So, yes, it seems that your intuition got it right and this is indeed the same problem. Let's hope Microsoft can do a fix-by-feature-gate-switch here as well.
Oh, and by the way, the instructions in your blog on https://www.accessforever.org/post/demystifying-microsoft-365-update-channels were extremely helpful in debugging this issue. 🙂
Hi,
Microsoft has confirmed the problem and that we can expect a fix soon.
This time, however, I have written a separate blog article about it to inform those affected and make them aware when the problem is fixed and that they will then have to update or more likely restart Access.
Servus
Karl
****************
Access Forever
Access News
Access DevCon
Access-Entwickler-Konferenz AEKHi,
Microsoft fixed the problem last night. There's no new build. You just have to restart Access to restore normal performance with the "SQL Server" driver.
I have also updated our documenting blog article. As written there, it would be good if affected users could briefly report back whether the fix works for them.
HeinziAT Extremely bad luck with this unusual order of appearance of the bug. S*** happens. At least you contributed to a quicker fix by reporting it here.
Servus
Karl
****************
Access Forever
Access News
Access DevCon
Access-Entwickler-Konferenz AEKKarl_Donaubauer How could Microsoft have fixed the issue remotely without some kind of release? This makes it sound like they have remote access to our systems?
Is there a support article about this?
