Very Computer

Rick Griffy, MCP

A timestamp data type in SQL Server is not a datetime data type. A timestamp
data type bears no relation to a date and or a time. So I'll assume that you are
referring to a datetime data type.

It is also unclear just what you mean when you say that the value changes. If
you are saying that when you query a row in a table it returns 1AM, but, without
changing the data, a later query returns 1PM, then you have, or more properly,
Microsoft has a major problem. Data stored in a table can not, must not change
unless an update is applied to the row.

If you are saying that when the data in **entered** into the table, the value is
sometimes entered as 1AM and sometimes as 1PM, my first guess is that the SQL
(the code) is not running on your SQL Server inside a stored procedure, but
rather from a client application, and the client application is pulling the date
and time from the client machine. Perhaps you can track down which rows are in
error, and see if they can all be traced to one or a handful of client machines.

---------------------------------------------------------------
BP Margolin
Please reply only to the newsgroups.
When posting, inclusion of SQL (CREATE TABLE ..., INSERT ..., etc) which can be
cut and pasted into Query Analyzer is appreciated.

Quote:> Occassionally our SQL 7.0 sp1 on NT sp5 will change the time stamp on a
> record from say 5-8-00 01:00:00 to 5-8-00 1:00 pm. It has also gone from
> 13:00 back to 1:00  am. This occurs at no particular date or time. A partial
> solution seems to be to leave the SQL server logged in all the times. We
> have already set all computers on our network to 24 hour clock. We also
> hacked the registry and set all Default settings to 24 hour.
> HELP!!

> Rick Griffy, MCP