Hello. I have a SQL 2005 job that runs every 2 hours in the morning. If it
runs to completion at any time I set a flag to tell subsequent instances not
to run. Works fine. The job normally takes about 1 hour. So what if, for some
reason, the job is running longer than 2 hours and the next instance gets
queued to run? Will this same job try to run if an earlier instance is still
running?

I know the MS Scheduler won't but what about the SQL 2005 Agent? I suppose I
could just test this scenario but I'm sure someone up here knows.

Thanks,
Ken Trock