Long running background maintenance
Aldevinas Katkus
3-13-23
Operating system: Windows
Can we write a maintenance which updates DB without affecting logged in users?
I can see AmazonImportOrdMn() calls qupdating procedure.
Also I can see some threadasync calls in NexmoSIPTrunkNSMn().

Should threadasync calls work better (not affect the work of logged in users) if the maintenance is deleting a million(s) of old RHistVc records for about an hour or more?

Reply
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Latest Posts
qupdating collisions
Paul Timms
I've found an issue which I'm trying to find the best way to resolve. An integrated proof of delivery system sends two pieces of data to the SERP API, in two separate calls - let's c...
17:59 20 Feb 2026
Optional Features > Idle Client Timeout
Andis Blicāns, Grasko
There are some topics in this Q&A related to this question, but none of them is about Idle users - Concurrent or Named. If timeout minutes are specified in Optional Features, then all idle users are...
15:53 18 Feb 2026