When I run some scripts that do things (like purge type 1 records from the
calls table or total user hours or anything that runs for a while) it seems
to run at too high of a priority on the SQL server and so my radius
accounting information is timing out and logins are really slowed down by
quite a lot because the server is busy.
Is there a way to run an SQL script so that it runs as a low priority task
and doesn't hog the whole server? Anyone?
Geo.