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 |
|
rockmoose
SQL Natt Alfen
3279 Posts |
 Posted - 2005-04-12 : 04:16:30
|
Did anyone ever have an issue with missing rows during DTS import of a Textfile?.We have a DTS import of several textfiles on a network share.(15 files in all)It has been running monthly without any problems for more than 3 years.This month, the text files were created at 00:20 AM, and imported at 00:40 AM. However in some of the tables there was missing data !?I reran the exact DTS package with the exact same files once again and got a correct result. 3 of the tables had missing rows:TABLE1 732573(1st run of DTS), 840368(2nd run)TABLE2 29739(1st run of DTS), 34521(2nd run)TABLE3 312(1st run of DTS), 322(2nd run)Anyone else seen this ?, or has an explanation ?I have been thinking about replacing the DTS packagewith bcp/BULK INSERT for a long time...Maybe now is the time  ...rockmoose |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-04-12 : 12:19:56
|
| I haven't tried to import text files with DTS - only ever used BCP for that job.DTS with Excel stinks - lots of opportunity for lost data 'coz the DTS driver only looks at the first few Excel rows before deciding "how big" each column might be.Is it possible that the Files were NOT finished creating / not closed when the Import started? In those sort of situations I create the files in a different folder and then MOVE to the required folder - thus they are not available in the Required folder when only half-built.Can the providing source provide a checksum of expected rows, or somesuch, so that the importing tool can be 100% sure its got all the data?Kristen |
 |
|
|
rockmoose
SQL Natt Alfen
3279 Posts |
Posted - 2005-04-13 : 17:29:08
|
I was also thinking that the files were not complete when the import started,ore some similar explanation.They are delivered from a mainframe by some software "decapus", a "message broker"...Oh well, we'll see what happens next time.Fixing something "partially" broke is not a priority at the moment.If it breaks a couple of more times, then we'll fix it.  This particular import as I said has worked for years, so we'll see if it was just aone time circumstancial fluke error.rockmoose |
|
|
|
elwoos
Master Smack Fu Yak Hacker
2052 Posts |
Posted - 2005-04-14 : 03:07:40
|
| Stupid question I'm sure but does your DTS log its errors? steveA sarcasm detector, what a great idea. |
|
|
|
rockmoose
SQL Natt Alfen
3279 Posts |
Posted - 2005-04-14 : 08:59:11
|
Yes, all ok in dts logs.(but thanx for the suggestion, I almost never look in those logs  )(actually we only set up dts logging for some packages)Mostly the packages are run by a master sp, that runs any packages / procs in a particular batch.We handle most logging from within the dts/sp themselves.rockmoose |
|
|
|
elwoos
Master Smack Fu Yak Hacker
2052 Posts |
Posted - 2005-04-15 : 03:06:30
|
| Must remember to look in mine too :)steveA sarcasm detector, what a great idea. |
|
|
|
|
|
|
|
|
Missing Rows DTS Text Import