Page 1 of 1

SQL Server Timestamp problem

Posted: Mon Jun 13, 2005 10:34 am
by satish_valavala
I am trying to load a SQL Server table from another SQL Server source table (Its a direct copy). Source table is having three timestamp fields. While Viewing source data form Dynamic RDBMS stage, I am able to view data (including timestamp, in the format of 2004-11-23 00:38:24.000).
While running this job its failing by throwing these warnings,

Dynamic_RDBMS_12,0: Warning: Dynamic_RDBMS_12: [DataDirect][ODBC SQL Server Driver]Datetime field overflow

Dynamic_RDBMS_12,0: Warning: Dynamic_RDBMS_12: create_id = 999503 create_date = 2004-12-22 0:12:33.0 edit_id = 112233 last_edit_nm = xyz administrator edit_dt = 2005-12-21 0:12:33.0 changed_dt = 2005-12-22 0:12:33.0 assistant_nm = NULL company_list_id = 0 comments = NULL tran_src_id = 2 sys_id = 1234567 src_id = 1 ia_edit = 0 reserved = ~40,4~ contact_score = NULL

could anyone figure out why this is happening.

Posted: Mon Jun 13, 2005 3:17 pm
by ray.wurlod
If your TimeStamp format is the default

Code: Select all

%yyyy-%mm-%dd %hh:%mm:%ss.x
then you will require two digits in the hour component. Check also that you have a TimeStamp format that includes fractional seconds.

Posted: Tue Jun 14, 2005 6:12 am
by roy
Hi,
I wonder what a date looks like when yo have a 2 digit hours?
Is it still having the .0 in the fraction or not?
Things like that might be also configured on the DB server or ODBC configuration side rather then DS.

For finding work-arounds for Data Direct odbc drivers explore the branded_odbc directory ( $DSHOME/../branded_odbc)

IHTH,