Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
simondeutsch
Aged Yak Warrior
547 Posts |
 Posted - 2002-11-20 : 12:32:18
|
| I am trying to DTS several dBase III tables into SQL Server 7, and the job fails with this message:"Error at destination row 3144....." Insert Error, column 3 (Del_Date,DBType_DbTimeStamp)Status: 6 Data Overflow. Invalid character value for cast specification"The Del_Date value on that row is seemingly innocent 10/29/98. Similarly, this problem is occuring for other tables, on other regular-looking dates. I can see no regular pattern, as some other tables using dates transfer completely.Any Clue?Sarah Berger MCSD |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-11-20 : 12:38:22
|
| is it expecting mm/dd/yy in which case all your other dates will be wrong too.Try importing into a character field and converting or using converting the data in the package.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
simondeutsch
Aged Yak Warrior
547 Posts |
Posted - 2002-11-20 : 12:49:12
|
| It is getting it in mm/dd/yyyy format. Out of a table of 135,000 rows, it targeted approx. 25 as overflowing, all of which had correct dates. When I get into the dBase table and retype the date, it will no longer get the error on that row.Sarah Berger MCSD |
|
|
|
simondeutsch
Aged Yak Warrior
547 Posts |
Posted - 2002-11-20 : 13:13:14
|
| Even Odder: When I split the tables into smaller tables and transfer the smaller tables, it works.Sarah Berger MCSD |
|
|
|
simondeutsch
Aged Yak Warrior
547 Posts |
Posted - 2002-11-20 : 13:29:14
|
| Another observation: the error of "Data Overflow" here does not seem to apply to the column's value. I think its the memory or buffer DTS is using- on one particular table, the error always occurs on row 16312, although 16312 is not always the same row since the table was split up into smaller tables. The split tables containing 15,000 rows transferred, and I tried to dump the remaining 43,000 rows into another table and transfer it, and voila! Got this error again!Sarah Berger MCSD |
|
|
|
|
|
|
|
|
Date foolishness from dBase III to SQL Server