Post reply

Daylight saving time and SQL agent job

  • March 14, 2013 at 11:16 am

    #1597164

    dan-572483 (3/12/2013)

    sqlfriends (3/12/2013)

    dan-572483 (3/12/2013)

    Good general rule: Jobs that need to run once but NOT more than once should not be scheduled between 1 & 3am on Sunday mornings.

    But I don't think any of jobs need to run twice

    I was thinking of transaction log backups, which we run several times an hour. Within the context of this discussion we don't need to worry about them.

    I believe it was found that when we "Fall" back t logs stop being backed up for an hour as the Next run time is set at the start of the job to be say 2:01 which does not happen for another hour after 1:59. (thinking back from last year and ill try to dig up the thread.)

    EDIT: Found the thread http://www.sqlservercentral.com/Forums/Topic1264622-391-1.aspx Yes the KB article is old but its what i had found at the time.

    Also makes me want to use UTC times with no Time zone offset and a table holding UTC Offset where i need it so i dont rely on the server time totally for the DateTimes and can then not have my servers automatically adjust for DST and not have to worry about this stuff.

    For faster help in answering any problems Please read How to post data/code on a forum to get the best help - Jeff Moden[/url] for the best way to ask your question.

    For performance Issues see how we like them posted here: How to Post Performance Problems - Gail Shaw[/url]

    Need to Split some strings? Jeff Moden's DelimitedSplit8K[/url]
    Jeff Moden's Cross tab and Pivots Part 1[/url]
    Jeff Moden's Cross tab and Pivots Part 2[/url]

Viewing post 16 (of 15 total)

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