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 |
|
Van
Constraint Violating Yak Guru
462 Posts |
 Posted - 2008-09-05 : 16:46:59
|
| We have a new process that was set up to import a text file (tab delimited). The text file has 81255 rows in it and it's around 150 columns wide (the table is as well). When the SSIS package runs it only imports 40626 records and then finishes successfully with no errors whatsoever. I can open the text file, go to record 40626 and get the value for the PK in the table and see that the record is in the table but the row for 40627 isn't. So it seems that something on that row (40626) is stopping it and making it think it's done. The row looks fine. My boss has viewed it with a hex editor and can't see anything wrong. Anybody have any idea what would cause this to happen?Thanks,Van |
|
|
Van
Constraint Violating Yak Guru
462 Posts |
Posted - 2008-09-05 : 17:31:53
|
| Figured it out. The person that developed the SSIS package messed up on the columns and it was importing the first couple of fields of the following row and skipping it and so on. That's why only half of the records were getting imported. I would have thought it would give an error but they may have the errors disabled. |
 |
|
|
|
|
|
Strange issue with text file