July 13, 2018 at 10:23 am
I'm running SSIS on 2012. I have over 3 million rows in the source flat file but my dataflow is only processing 1.6 million into a sql server table. I'm using a OLE DB destination and a flat file source, when I look at the log it shows the correct number of rows in the souce file, but when it runs it doesn't throw any errors, it looks like it finishes normally and stops at the same number of rows each time. There is a redirect for error rows but nothing is getting sent there, I have all fields set to redirect on error and truncation. I've looked at the data input file for clues and I don't see anything wrong with the row it is stopping at. Can anyone help?
July 13, 2018 at 10:39 am
vicki.l.lucht - Friday, July 13, 2018 10:23 AMI'm running SSIS on 2012. I have over 3 million rows in the source flat file but my dataflow is only processing 1.6 million into a sql server table. I'm using a OLE DB destination and a flat file source, when I look at the log it shows the correct number of rows in the souce file, but when it runs it doesn't throw any errors, it looks like it finishes normally and stops at the same number of rows each time. There is a redirect for error rows but nothing is getting sent there, I have all fields set to redirect on error and truncation. I've looked at the data input file for clues and I don't see anything wrong with the row it is stopping at. Can anyone help?
Can you split the source file into two and try processing each individually?
At least that should answer the question about whether there is something wrong with the data (this would be my guess, despite the lack of errors), or whether it is the sheer volume of data which is causing issues.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
July 13, 2018 at 11:01 am
Could it possibly be a timeout issue? I think I've seen similar behavior in SSIS when there is a timeout in the source of a dataflow, it doesn't necessarily halt the execution and you can get a partial load then.
July 13, 2018 at 11:15 am
Chris Harshman - Friday, July 13, 2018 11:01 AMCould it possibly be a timeout issue? I think I've seen similar behavior in SSIS when there is a timeout in the source of a dataflow, it doesn't necessarily halt the execution and you can get a partial load then.
Also - you might care to open the file in a text editor and look for any "odd" extended characters. You may be hitting something the SSIS interprets as EOF (end of file). That's character code 26 in ASCII.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply