Date time overflow problem

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
mydsworld
Participant
Posts: 321
Joined: Thu Sep 07, 2006 3:55 am

Date time overflow problem

Post by mydsworld »

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
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

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?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
mydsworld
Participant
Posts: 321
Joined: Thu Sep 07, 2006 3:55 am

Post by mydsworld »

So, what would be the timestamp for '0001-01-01 00:00:00' that would be accepted in SQL Server.

Thanks.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

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".
Post Reply