June 30, 2014 at 10:36 pm
Running visual studio bids 2008 as Administrator.
Very simple data extract txt files to SQL Server tables. Preview in Flat File Source connection and Flat File Source showing data in rows, no errors or symbols indicating errors, and when I run all boxes go green, but when I check ole destination data flow task, no data in preview... and in destination sql server tables, no data imported. Unicode coming in, set nvarchar(max) on destination...etc. no errors whatsoever. Just in the execution results I get the following:
"[Flat File Source [1]] Warning: The end of the data file was reached while reading header rows. Make sure the header row delimiter and the number of header rows to skip are correct."
I've set the 'number of header rows to skip" as 0. I've tried every header row delimiter, though source file doesn't have any characters, just looks like a Carriage Return though don't know how to be sure.
Why no rows of data coming over when every file has something to import??
July 1, 2014 at 1:42 am
Try adding a dataviewer to check that your data is as it should be.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
July 1, 2014 at 6:19 am
Phil, yes, I did and no data leaving FF Source so nothing to examine even. Preview in flat file connection manager showing data as it should be.
I have read through this post http://www.sqlservercentral.com/Forums/Topic996796-364-3.aspx?Update=1 and description of my problem is nearly identical to mine except my source is flat file. I tried ADO NET destination connection, for example, and made no difference.
Another thing I tried was to consume the FF as one column. Since the delimiter is so strange I wanted to eliminate that. That made no difference.
Execution results repeatedly say same thing:
[Flat File Source [64]] Warning: The end of the data file was reached while reading header rows. Make sure the header row delimiter and the number of header rows to skip are correct.
[Flat File Source [64]] Information: The total number of data rows processed for file "C:\Users\me\Downloads\2014-06-20_24632_1403294306_settings_account.txt\2014-06-20_24632_1403294306_settings_account.txt" is 0.
Would love additional ideas....
July 1, 2014 at 6:42 am
I would edit the file using a decent text editor - say Notepad++ - and confirm your row delimiter (in Np++ select View/Show Symbol/Show All Characters).
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
July 1, 2014 at 6:49 am
Another quick thought - what is the codepage associated with the Flat File connection manager?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
July 1, 2014 at 7:19 am
Can you please see if you can do a straight across pull?
<<<I've attached one of the files I'm trying to consume. Can you please try straight pull and push to test table and see what happens. I even tried in VS2010 to see if different BIDS version made difference. Note the delimiter þ is created by hitting alt + 0254. This only works if you have a number pad. It will not work if you press alt and type those numbers using top row of numbers of a small featureless laptop, for example:-).
more background:
Regarding code page: 65001 (UTF-8). When I was initially setting up this package, (before I knew I would have this problem) I was getting a more primordial error that I can't have source and destination using two different code pages and I followed directions to set the property "AlwaysUseDefaultCodePage" on destination to true. When that didn't resolve error I converted all destination columns to Unicode ie. nvarchar(max) which made errors go away. After encountering this problem I toggled this property to see if it did make difference. It did not and it seemed that Unicode issue was the actual issue (even though I'd dealt with unicode issues before and hadn't seen this kind of error). Currently, codepage on FF source connection manager is 65001 and on destination set to use default though if left alone, would apparently be 1252.
July 1, 2014 at 9:45 am
Well this is an interesting one.
I was unable to get that damned delimiter working, even though all looks fine in 'Preview' mode, as you found.
If you do a 'replace all' and change þ to | (pipe), all of your problems go away.
Is there an option to modify the delimiter? If not, more investigation is needed, focused on exactly what is happening with that delimiter.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
July 1, 2014 at 10:03 am
Thanks so much for discovering and testing that. I didn't think to try that even tho error said it came to end of document without finding end of row. I fixated on row instead of colomn delimiter. . Thanks so much. Yaaay.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply