SSIS data flow task not loading all rows from sybase server
Hi, Using a data flow task I am trying to load data from a table in sybase server to sql server. There are approx 10000 rows in the sybase table, however for some reason which I am not able to find out, at random certain no of rows are getting inserted. e.g. in one run 800 rows then 200 rows etc. Can somebody please guide me on this?
October 15th, 2010 5:43pm

What is the query you are using. Could there be some filter condition. What about the error rows? have u handled them? Have you set the error rows to e redirected? Tweet me..
Free Windows Admin Tool Kit Click here and download it now
October 15th, 2010 5:46pm

I am using a simple query "select * from table_nm", there aren't any filter conditions specified. I haven't handled the error rows, the package is executing fine as I have configured the error output to "Fail Component" on error. Thanks,
October 15th, 2010 6:24pm

Can you check the SQL profiler to see whats happening behind the scene? What are the transforms that you are using? By any chance are you using a conditional split or any other task like lookup or something which may be removing the record. Are you using GETDATE() function in data flow task and then filtering the data?? Can you tell us more about your data flow task. another question: when running the same file over and over again are you getting differeten number of records in the output or the same? These are just ways of trouble shooting.... Tweet me..
Free Windows Admin Tool Kit Click here and download it now
October 18th, 2010 2:30am

Hi Sherin, As you mentioned, you loaded the data from Sybase to SQL Server without any conditional split or any other task. So, the issue might be caused by the data was not loaded correctly from the Sybase or not inserted the SQL Server correctly. In Sybase side, based on my search, it seems there is a MDA table that will help us to find what T-SQL is passed to the Sybase. Please check if the T-SQL is correct, and check the result the T-SQL returned in the Sybase. In SQL Server side, please follow Sudeep's suggestion that using the SQL Server Profiler to check what happens. Additionally, we can use a Data Viewer in the Data Flow Task to check the returned data. Thanks, Jin ChenJin Chen - MSFT
October 21st, 2010 8:27am

Hi, It seems this happened because of the sybase provider (Sybase OLEDB Provider) I was using, I tried by using a different provider (Sybase ASE OLE DB Provider) and it worked fine. However I still wondering how can this be explained in logical manner!
Free Windows Admin Tool Kit Click here and download it now
October 21st, 2010 11:19am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics