November 29, 2002 at 2:39 pm
Just a curious, survey type set of questions:
Does anyone use Run-When-Idle jobs and if so, what are some uses for it you've found in your environment? Also, what are some of the settings you use for deciding what is an idle state?
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
November 29, 2002 at 3:04 pm
I dont, curious to hear what uses people have for it as well.
Andy
November 29, 2002 at 8:08 pm
I saw it used once in a company I worked for. They used it for archive jobs which removed rows one at a time based on a datetime field. It was a very high transaction system, which had to be up 99.8 percent of the time, and had a very high number of scheduled jobs as well. I can't say whether it was a good way to do it as I never got a chance to look into it much (I was assigned to a different project), but through talking with the DBA in charge of that database, got the impression that it was adequate for the purpose. He explained that the archive functions were not mission critical, but something which could run just whenever, and to save him from having to find time to do it, he set it up this way, and just checked it so often to see that it was doing its job. He did mention that on occassion he had to clean up anyway, but that it simply reduced the amount needed.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply