This past weekend, a client of our company noticed that the timestamp in the tables within their database was off by one hour. Although NT adjusted for daylight savings, SQL server did not. We have stopped and started SQL server and still no success. Does SQL Server have it's own internal clock and if so, is there are setting where we can set the time in SQL server equal to the NT time?

Thank you for your assistance

-- Anonymous, April 06, 1999

Answers

Kimberley,

I will have to do a little more research, but in the meantime, try rebooting the server. It never hurts and is needed every 49.71 days anyway.

Eric

-- Anonymous, April 06, 1999

Kimberley,

This is the biggest hint I can find: Windows NT updates its internal date and time every hour by reading the CMOS on the motherboard. In between the one hour intervals, Windows NT increments its own clock approximately every 10 milliseconds. Because Windows NT cannot detect when the system BIOS/CMOS (hardware level) adjusts the clock for daylight savings time, it may change the clock by one hour, just as the BIOS does. This causes your computer clock to be one hour ahead in the Spring or one hour behind in the Fall after both your computer's BIOS and Windows NT adjust the clock for daylight savings time.

This may explain why the SQL time is different from the NT time.

If you are still having this problem, please post another message to this forum stating which version and service pack of SQL Server (and NT) you are running.

Hope this helps,

Eric

-- Anonymous, April 12, 1999