Hi,
I am trying to load a Timestamp field into a table in SQL server database.
It is giving error 'Date time overflow ...'. I checked the incoming timestamp value. It is like '0001-01-01 00:00:00'. However, I am able to load the field with CurrentTimestamp() value.
Please let me know whether SQL server has any restriction on such timestamp value.
Thanks
Date time overflow problem
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Can SQL Server handle the timestamp 0001-01-01 00:00:00 successfully?
There is a problem with the year 1AD because the previous year is not 0AD - there is no such year - the previous year is 1BC. Therefore the transition through midnight is not properly defined. Can you try 0001-01-01 00:00:01 as the timestamp?
There is a problem with the year 1AD because the previous year is not 0AD - there is no such year - the previous year is 1BC. Therefore the transition through midnight is not properly defined. Can you try 0001-01-01 00:00:01 as the timestamp?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Did you try the "0001-01-01 00:00:01" as Ray suggested and did that work? If yes, then the answer is that you cannot represent "0001-01-01 00:00:00".
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>