Running Querries during the day

Mar 28, 2007 2 Replies
T

Running SELECT queries should be OK at any time.

It's those UPDATE, INSERT and DELETE queries that you worry about...

Against my own better judgement, I often execute UPDATE, INSERT and DELETE statements during the day. For example, when closing a billing cycle there are inevitably a few accounts that have the dreaded Last Closing Balance error. I run those queries right away from HQ Admin without even backing up.

I have inserted Alias records en masse during the day. (with backup)

I have made mass ILC changes during the day. (with backup)

Tom

Vote
Twitter Facebook LinkedIn
K

Is there any harm in running querries in Administrator during the day while POS is in use? I've always assumed we shouldn't do it, but just wondered if it might be safe. I always backup first.


Vote
Twitter Facebook LinkedIn
G

It depends on the query in too many ways for me to even begin listing... The main danger is locking. You can write select queries so that they don't lock anything - in that case you're safe, except for the memory and CPU cycles that your query takes to execute. Every query has a cost. If you have high transaction counts in your location, even a 'safe' query may reduce performance while it runs. Any query you run that locks tables or rows has the potential to cause a 'deadlock' - you do not want a deadlock...

Generally Selects are safe if your database server has power to spare; Inserts, Updates and Deletes are never safe.

Glenn Adams Tiber Creek C> Is there any harm in running querries in Administrator during the day while

Vote
Twitter Facebook LinkedIn

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required