July 12, 2013 at 2:50 pm
Hi every one
I'm working with SQLServer Integration Service 2008
I have some questions about handling fails in SSIS:
I have a package containing a data flow task, wich has some data flow sources, transformation, and destination, but without handling error the task stops displaying the error cause in the output window, the error message is very clear, like this: Hresult: 0x80004005 Description: "Violation of UNIQUE KEY constraint ...."
When I try to handle the fails for logging messages, I try to capture manipulating "Oledb destination error output" looking for that error, but that message is hidden and always returns this ErrorCode -1071607685 with the message "Not status available", and the columnNumber is 0. That is the same for any sql server error occurs.
I need to capture sql server errors from ssis package, code and message, not ssis package errors, this is for logging that messages in a database.
Thanks for any suggestion.
Jose Obregon
July 13, 2013 at 10:20 am
Not sure exactly what you've got in place but I sense a bit of misunderstanding in what you're saying. When you redirect the error output from an OLE DB Destination you get the opportunity to handle those rows again. When you handle errors in an OnError Event Handler, that is where you might see the actual error message coming back from re database. Either way you won't necessarily be able to tell exactly which row caused the error if your Commit Size is greater than 1.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
July 15, 2013 at 11:42 am
Hi opc.three
thanks for your suggestion about "OnError Event Handler". It is exactly how you said.
thanks very much!.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply