SQL Job Schedules

  • HappyGeek

    SSCoach

    Points: 18676

    Comments posted to this topic are about the item SQL Job Schedules

    ...

  • This was removed by the editor as SPAM

  • Koen Verbeeck

    SSC Guru

    Points: 258955

    Nice question, thanks.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Ed Wagner

    SSC Guru

    Points: 286969

  • Megistal

    SSCrazy Eights

    Points: 8787

    Ok but why does it works like this under the hood? Why 20 minutes? Why on schedule?

    msdn web page is not very chatty about it.

    https://msdn.microsoft.com/en-CA/library/ms188924.aspx

  • Marcia J

    SSCertifiable

    Points: 5645

    Megistal (11/17/2015)


    Ok but why does it works like this under the hood? Why 20 minutes? Why on schedule?

    msdn web page is not very chatty about it.

    https://msdn.microsoft.com/en-CA/library/ms188924.aspx

    Just what I was wondering.

  • patricklambin

    SSCrazy Eights

    Points: 9964

    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.

  • Hany Helmy

    SSChampion

    Points: 13436

    That was new 4 me, thanx

  • x

    SSC-Insane

    Points: 23533

    patricklambin (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 🙂

  • patricklambin

    SSCrazy Eights

    Points: 9964

    patrickmcginnis59 10839 (11/18/2015)


    patricklambin (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

  • x

    SSC-Insane

    Points: 23533

    patricklambin (11/19/2015)


    patrickmcginnis59 10839 (11/18/2015)


    patricklambin (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

    I don't think you made any error though, because you got the question right and I didn't, so if anybody made an error it was obviously me 🙂 We both learnt today and that's what counts right?

  • akljfhnlaflkj

    SSC Guru

    Points: 76202

    Megistal (11/17/2015)


    Ok but why does it works like this under the hood? Why 20 minutes? Why on schedule?

    msdn web page is not very chatty about it.

    https://msdn.microsoft.com/en-CA/library/ms188924.aspx

    I wondered that too.

Viewing 12 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply