Re: Delimited Text File import problem
- From: Allan Mitchell <allan@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 10 Jan 2006 13:08:09 -0800
Hello John,
I think every tool imports files differently and each is tolerant of things that makes the others fall over. Can you isolate the rows that cause the failures? Does this file fail parsing so it never gets to the import? I generally try to isolate bad rows and then look at them in a HEX editor so i can see the unseen problems a lot of the time. There is no reason if a file is formatted correctly whay SQL Server DTS should have a fit.
Allan
We are using DTS Text File packages to import data into SQL Server tables. We have run into a problem with a particular file. This ~5000 lines file fails on parsing for no apparent reason. If we try to import the file directly using the DTS Wizard Text File Import, the preview screen hangs after we enter the delimiter character and click Next >>. We have tried changing the delimiter character to a standard comma, semicolon, vertical bar, etc and all same error. If we edit the file keeping the format and encoding (Unicode) and cut and paste 1 or 10 or 100 more lines into file, the file parse correctly in the preview window. If we remove 1 or 10 or 100 lines it parses correctly. The file as is also imports fine into Excel. It seems that the file as is will not import with the DTS Import Text File. We are stumped.
Any comments suggestions welcome.
Thanks in advance.
.
- Prev by Date: Re: Saving SSIS Packages
- Next by Date: Re: Saving SSIS Packages
- Previous by thread: Re: SSIS - Creating an XML File
- Next by thread: Re: Derived column data flow transform
- Index(es):
Loading