job run when idle

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

cbtechlists@gmail.com - 20 Mar 2008 13:48 GMT

I'm trying to get a SQL Agent scheduled job working using the Schedule
Type of 'Start whenever the CPUs become idle', but it doesn't seem to
be working.

I setup a maintenance task to check db integrity (as a test), set it
to run today in about 2 minutes, changed the Schedule type to 'Start
on idle' and the 'Define idle CPU condition' and watched CPU
utilization and the monitor to see if it runs, but it never does.

What step am I missing?

Thanks!

Chris

Reply to this Message

Linchi Shea - 20 Mar 2008 14:44 GMT

I don't use this feature, and don't know anybody who uses this feature
(though that doesn't mean nobody uses it). The reason is that for a SQL
Server job, it's better to know when it'll run than it is to leave it to
'random' chances.

Linchi

> I'm trying to get a SQL Agent scheduled job working using the Schedule
> Type of 'Start whenever the CPUs become idle', but it doesn't seem to
[quoted text clipped - 10 lines]
>
> Chris

Reply to this Message

Sean - 20 Mar 2008 15:31 GMT

I'm with Linchi, CPU utilization jobs generally shouldn't be used. I
would use the performance counters on the machine to keeps a log for
an average day/week of work and design a date/time strategy around
that. It should give you the best times to run these types of things,
i.e. low cpu + low I/O + low users @ 4:00 am everyday. Also take into
account any data loads or batch executions of programs or ones that
users manually do.

> I don't use this feature, and don't know anybody who uses this feature
> (though that doesn't mean nobody uses it). The reason is that for a SQL
[quoted text clipped - 20 lines]
>
> - Show quoted text -

Reply to this Message