Not too long ago, we had an upgrade issue at a customer: the upgrade timed out, and after investigation, it was simply because our upgrade code: it took too long to modify 130000 records (well – and quite some validations, I admit, but still – it’s not that much, is it?).
This made me hold on to some things that I had been doing even for my own apps (like the waldo.BCPerftool (which I’m now…
Continue Reading waldo’s Article on their blog
A Business Central “Upgrade Code” saga…
Not too long ago, we had an upgrade issue at a customer: the upgrade timed out, and after investigation, it was simply because our upgrade code: it took too long to modify 130000 records (well – and quite some validations, I admit, but still – it’s not that much, is it?).
Blog Syndicated with waldo’s Permission
More About This Author
Array
Business Central28 March 2024Rec.LockTable – Good Practice? Or Bad Practice?
Business Central27 February 2024Telemetry and Companies
Business Central31 January 2024Microsoft Dynamics 365 2024 Release Wave 1 plan for Business Central
Business Central28 December 2023Speed up your automated tests without really doing anything..
