My SQL 2000 server seems to be logging data an hour early, the Windows 2003
time is correct though. What steps should I take to find out what is
happening. I'm in the UK and we have to change our clocks for day light,
but these are all set to automatically adjust clocks.
Should it be using the local server time?I had a discussion with an Microsoft Consultant about this, from what I
remember. He said SQL server doesn't have time-zone setting it grabs it's
information from the Server its running on. So maybe check the settings on
the server ..
Ref Link: http://support.microsoft.com/?kbid=928388
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Gonzo" wrote:
> My SQL 2000 server seems to be logging data an hour early, the Windows 2003
> time is correct though. What steps should I take to find out what is
> happening. I'm in the UK and we have to change our clocks for day light,
> but these are all set to automatically adjust clocks.
> Should it be using the local server time?
>|||SQL Server gets it date and time from the server itself thru an internal
winapi call. So if the server is correct then so is SQL Server. If you are
supplying the datetimes via the client as a value in the insert statement
then the client may be an hour behid. Can you post the actual code that is
doing the inserts?
--
Andrew J. Kelly SQL MVP
"Gonzo" <no@.no123.com> wrote in message
news:CF181373-2F00-4EE0-9B7F-6EAC76C705BE@.microsoft.com...
> My SQL 2000 server seems to be logging data an hour early, the Windows
> 2003 time is correct though. What steps should I take to find out what is
> happening. I'm in the UK and we have to change our clocks for day light,
> but these are all set to automatically adjust clocks.
> Should it be using the local server time?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment