patrickmcginnis59 10839 (11/18/2015)
Thanks for this interesting question. I have been able to answer it only because I have studied jobs ( and used them ) in September.
As several posters , I am surprised by this value ( 20 minutes ) which I am considering as short and maybe wasteful in resources but I am far to be a specialist of this topic that I have used scarcely since the 2008 / 2008 R2 versions.
I was surprised in the opposite direction, as in, I wondered why this wouldn't be updated every time something changed, like a new job being scheduled, or a job finishing execution. Obviously not a server implementer here 🙂
As I wrote in my post , my knowledge of jobs is coming from the time I have installed my SQL Server 2008 ( not R2 ). As I am curious , I have used jobs to be not ignorant about this topic , but I have not used it since 2010 except a little on September. It is why I have written that I am far to be a specialist. About your reply , you gave good reasons which push me to consider that I have been wrong.
I will restart to use jobs later as I have several problems with an old application using SMO and I don't like to give up something before having tried to finish a task in the most full way ( even if perfection is impossible ).
Anyway , thank you to have pointed my error. I have learnt something today and that it is the most important point according to me.
Have a nice day