2

Result of sp_Blitz:
Finding = “Server Last Restart” ; Details = “Feb 11 2017 5:48AM”
Finding = “SQL Server Last Restart” ; Details = “Feb 11 2017 4:48AM”

SQL Server Last Restart is the tempdb create_date
Server Last Restart is the ms_ticks

I find the results odd because, SQL Server Started an hour before Server Restart?
enter image description here Am I missing something here?

Improve this question
3
  • Exactly 1 hour... I wonder if this is due to Daylight Saving Time?
    – Scott Hodgin - Retired
    Commented Apr 7, 2017 at 15:03
  • Is your server in a time zone that observes Daylight Saving Time? Looks like the Server Last Restart has been adjusted for the "current" DST timezone, but the SQL Server Last Restart is in the unadjusted non-DST timezone.
    – AMtwo
    Commented Apr 7, 2017 at 15:04
  • The Server is in Central Time. However, I am wondering how can SQL Server read different time than Windows time !!
    – Santhoshkumar KB
    Commented Apr 7, 2017 at 15:30

1 Answer 1

Reset to default
3

I would 'suggest' that when the server was restarted (and Sql Server was also restarted) back on February 11, 2017, the current Windows time, which was Standard time and not Daylight Saving time, was captured as the Creation Date of TEMPDB (and that is what SP_Blitz uses to determine Sql Server restart time).

Now, you are running SP_Blitz AFTER the change to Daylight Saving time and sys.dm_os_sys_info (which is used by SP_Blitz to report Server Last Restart and appears to be Daylight Saving time aware) is affected by the time change, thus making it 'look' like the server started AFTER Sql Server.

Improve this answer
0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.