October 7, 2004 at 5:51 am
When I try to DTS a table from MS Access 2000 into SQL Server, I get the following errors on the columns that store dates in them:
"Insert Error, Column 3 ('DateRecieved', DBTYPE_DBTIMESTAMP), Status 6: Data Overflow"
Anyone know how to fix this? Thanks.
Michael
October 7, 2004 at 6:21 am
Have you verified that you don't have garbage dates? they are actually dates?
Good Hunting!
AJ Ahrens
webmaster@kritter.net
October 7, 2004 at 11:26 pm
Verify the column type... It should probably be DateTime but the conversion probably set it to SmallDateTime... This happened to me as well and the data type that it converted as was the issue.
October 8, 2004 at 6:59 am
I ran into this issue many times. It's an invalid date senario. In Access you can enter enything you want in a date field unless it has a input mask. Sort the date column in the Access table in (check on both ascending and descending) and it will float the garbage dates to the top or bottom.
October 11, 2004 at 7:43 am
Access will not allow you to enter a invalid dates in a datetime datatype field so if your Access field is a datetime field you will not have any invalid dates in it.
The timestamp data type in SQLServer 2000 is not the same thing as a datetime datatype. Timestamp is a database wide unique number that is updated everytime a row gets updated. It is a row version number. Change the DTS job to convert the Access datetime field to a SQL datetime field and you shouldn't have any problems.
November 17, 2004 at 8:07 am
Awesome everyone thank you. This fixed the problem I was having. I sorted dates in access tables and cleaned up junk dates...conversion worked for all tables!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply