SSIS Broke after 4 days of run !!!!!!!!!!!!!!!!!!!!
-
Hi
I have two big tables [Contain about 5 million rows] which are almost symmetric in schema[ Expect the second one carry PK value for referential integrity]. The data are actually copied using a SSIS. This SSIS is a ETL in nature which actually transform and copied data from source to destination database. This ETS involves many table in source and destination.
Now, after a long run, SSIS broke L with below error:
Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
While I took count of the tables, I found all the data are pushed perfectly except the tables I mentioned above. About 6000 rows are missing in target.
So
- Could any one tell me any TSQL/work around to fond what are the rows which are available at source but not in target?
- What can be the possible root cause of the error?
Thanks in advance for your help.
Regards
Utsab Chattopadhyay
- Could any one tell me any TSQL/work around to fond what are the rows which are available at source but not in target?
-
Utsab
If you're using Execute Task to move data using ODBC here is something you might wanna take a look at.
http://blogs.simplifi.com/brucet/archive/2006/01/27/668.aspx scroll to the middle.
To find missing data use this query and make sure to remove parenthesis
select col1 as missing_data
from tablesource ts left outer join tabledest td on ts.(your primary key) = td.(your primary key)
where td.(your primary key) is null
After you find the missing data create test tables and try to move data using SSIS.
Alex S -
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply