Datetime field contains impossible value

  • Hello,

    I have a datetime field in a table that has somehow got the value of 2003-11-06 24:01:59.917.  (there is not such thing as 24:01)  Does anyone have any ideas how this could have happened?  When I try to add or update a datetime field to an invalid time such as my example, I get an error.  I have a couple rows in a table with this problem.  Are there perhaps any regional settings that could have allowed this?

    Also, I am unable to update the time with an update statement, it says it ran successfully but it never changes the date or time.  I have to delete the line and recreate it.

    Any thoughts on how this happened are appreciated.

    Trent.

  • did you run dbcc to check any possible data corruption

  • A DBCC Check does report it as corrupt (although cannot repair it with any repair options), I am more interested in trying to figure out how this happened. 

  • Did you bcp data into the table at some point?  I believe there was a bug where bulk loading allowed impossible values into datetime columns.  An impossible datetime value is where the binary date component is greater than 0x002D247F (int:2958463) or less than 0xFFFF2E46 (int:-53690), or the binary time component is greater than 0x018B81FF (int:25919999) (as in your example) or less than zero.



    --Jonathan

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply