February 4, 201411 yr Apologies if this is a bit of an obvious question: I run a script across a found set to change the status flag of each record (The job can now be invoiced). This found set is itself defined by a status flag (The job can now be delivered). My concern is that while this invoice script is running, another user could be changing the delivered status and the script could miss a record. Is there a way to temporarily lock the whole database to everyone except one user - so that the script can be run without any other users modifying any data?
February 25, 201411 yr Apologies if this is a bit of an obvious question: I run a script across a found set to change the status flag of each record (The job can now be invoiced). This found set is itself defined by a status flag (The job can now be delivered). My concern is that while this invoice script is running, another user could be changing the delivered status and the script could miss a record. Is there a way to temporarily lock the whole database to everyone except one user - so that the script can be run without any other users modifying any data? Not sure but you can error check for whether the record was locked when the script tried to run and record the record id in a temp field somewhere for future reference. Alternatively run the script at night when you know no one is working?
Create an account or sign in to comment