March 8, 2016 at 5:34 am
Clocks are due to go forward soon, how does SQL agent deal with this??
We have some data loads scheduled to start at 1.30am - will this be impacted Should we look at moving the times outside of the 1am - 3am window?
March 8, 2016 at 7:12 am
A good practice to get into is setting all the server dates and times to UTC and then working with data offsets from there. You'll get much more consistent behavior and won't then have to worry about potential logic problems in the data when you lose or duplicate an hour of time.
Depending on how you have your server set up, you will see the time shift.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 8, 2016 at 7:26 am
Cheers Grant, do you definitely lose an hour with the agent with the clock goes forward?
So between 1am and 2am is lost?
March 8, 2016 at 7:35 am
Isn't the official time 3AM when it changes, but yeah, you'll lose an hour.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply