I have a script that is doing maintenance on a set of approximately 1 million records and other users are complaining that when this script runs (server side) that everything is slow in the database.
the table that this script is altering is not being used by any users.
the script is performing many tasks, but there are a few REPLACE steps where it cycles through all 1 million records. I was wondering if a replace locks the system down more than a loop with set field?
Using a loop / set field vs. replace is SIGNIFICANTLY slower for the script to complete, but I'm more concerned about the effect the other users feel while the script is running...