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 |
|
Jay99
468 Posts |
 Posted - 2001-03-14 : 11:18:29
|
| I am having some major frustration with a DTS package . . . Looking for some help.I have 3 100MB .csv files of data to be loaded into a SQL Server 7 (on NT 4.0) database table.These files contain all 'text' data, that is to say, all of the columns are of type varchar and in the .csv, the columns use the double-quote as the text qualifier.I have set up a OLE DB for SQL Server data destination in my package and I have a Text source for each of the data files.All three files have some (read: like 100 of the million or so records in the file) instances where there is a comma in the data, i.e. "field1","field2","field,3","field4" . . . etc.The first data file goes in just fine. Let me say that another way. The first data file goes in just fine.The other two error out, telling me:Error at Source for Row number 26562. Errors encountered so far in this task: 1. Error Source: Microsoft Data Transformation Services (DTS) Data PumpError Description:General error -2147209197 (80043013).Error Help File:sqldts.hlpError Help Context ID:0 Error Source: Microsoft Data Transformation Services Flat File Rowset ProviderError Description:Too many columns found in the current row; non-whitespace characters were found after the last defined column's data.Error Help File:DTSFFile.hlpError Help Context ID:0Sure enough, if I go to that line in the .csv (which takes about 10 minutes to open the damn 100mb file) it is a situation where I have a comma in the text. BUT, there are instances of the comma in the text in the first file, and it went in just fine.Now if I cut just that line out of the .csv and make a new .csv with just that one line . . . it imports fine. If I cut the problem line and the line before it out and make a new .csv with the 2 records . . . I chokes giving the same error. I have counted and recounted the number of columns in each of the rows and they are the same.I have tried using and ODBC datasource in my package rather than the OLE DB Provider . . . same deal . . same line.My next move is going to be to cut the problem line out of file 2 and put it into file 1 and see what happens, although I don't really know what that is going to tell me.I got a pissed off client and a pissed off boss, and I am at a loss.Please, someone tell me you have come across this b4 and all you have to do is . . . .Jay |
|
|
Gili
Starting Member
42 Posts |
Posted - 2006-01-17 : 06:21:07
|
| HI,i have the same problem someone have any idea? |
 |
|
|
X002548
Not Just a Number
15586 Posts |
|
|
Gili
Starting Member
42 Posts |
Posted - 2006-01-21 : 15:30:47
|
| well my problem is similiar to jay problem just that in my case my every row look like thisfield1|field2|field3|field4| . . . etc.i've just added to the DTS 3 new fields and i get this error:"Too many columns found in the current row; non-whitespace characters were found after the last defined column's data."i split th file and it works ok but why it cant take it in one file this is not a big file just 22,000 rows i have bigger files that works fine.anyone plz help .10x. |
|
|
|
Norwich
Posting Yak Master
158 Posts |
Posted - 2006-01-23 : 09:08:20
|
quote:
Use Access?
If you want your computer to be faster then throw it out of the window. |
|
|
|
|
|
|
|
|
DTS BE KILLIN' ME!!!!