February 19, 2010 at 2:34 pm
Like most DB applications, our applications are 24/7. Currently we require the application to be shutdown each day for data maintenance. We would like to instead create an Agent job that runs every x amount of time. This job would determine how busy the server is based on CPU, IO, etc (still trying to determine the best measurement) and then do x amount of data cleanup if the busy measurement is okay.
I have been hunting around for a solution and so far it does not look good. The utilization information you can get is cumulative and seems to become unreliable after a while. The idea of starting the job, getting the CPU info, waiting for a bit and then determining how busy the CPU was seems like it could get me in trouble on a busy server.
Has anyone tried this before? Any ideas on how to determine how busy a server is so you can make a decision on whether to do something or not? Seems to me this is not that unusual of a thing to do. (I.E. is the server not busy so I can do x thing.)
TIA,
John
(Another accidental DBA via software development)
February 19, 2010 at 2:50 pm
In SQLAgent you can schedule jobs to run only when CPU is idle (you define what you mean by idle)
---------------------------------------------------------------------
February 19, 2010 at 3:01 pm
Boy do I feel silly. I did not even look to see if SQL Agent could do something like that.
That will meet my needs.
Thanks again,
John
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply