Is there any issue with datastage to convert timestamp field? I have SQL server table as source and one of the field in that table is timestamp. When I view the data using Dynamic RDBMS stage I see extra 3 zero's added at the end. For e.g. SQL server shows timestamp field as 2003-09-30 14:30:20.497, where as datastage shows same values as 2003-09-30 14:30:20.497000.
No idea where last 3 zero's are coming from. This is happening for all timestamp fields and for all records. Does anyone know whats going on here?
Thanks for looking at it.
SQL Server
Moderators: chulett, rschirm, roy
Hi,
there should not be one that I'm aware of.
this might be caused by environment or precision issues.
Take a look at the ../branded_odbc directory (form you dshome directory)
there should be text file regarding all kinds of ODBC problems and work-arounds, you might find something there.
IHTH,
there should not be one that I'm aware of.
this might be caused by environment or precision issues.
Take a look at the ../branded_odbc directory (form you dshome directory)
there should be text file regarding all kinds of ODBC problems and work-arounds, you might find something there.
IHTH,
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org