March 15, 2019 at 1:02 am
I want to log and maintain each and every error generated when running my SSIS package either it is related to connections (source/destination), network, data selection or transforming to and when loading to destination.
There might be several articles for fulfilling my request. Are there any good article or samples available (it might be in peaces but does not matter), please share.
When running SSIS packages, several errors are possible and finding those on time is required to minimize the debugging and complete migration tasks. Assuming there are thousands of tables and several databases with different platforms. I want to have one same approach to be used for fixing errors once it is logging every possible error, we can implement the same for each package we build, would be saving time and efforts. Please guide.
Example:
The source has 100 rows but when exported to destination it exports only 85, 15 rows has detected error due to column size issue or invalid data, like invalid date format or the destination can't accept NULL but the source is sending null values. those rows should be logged in separate flat file by giving column name and reason with error details.
If the data is null or have size or type issue (row level) ...
Each package should have its proper file name if there are several tables, error date/time for logging purpose.
If someone has done this please share ....
I have made a sample but it does not log if the destination column does not accept null, it does not log into flat file ...
A sample dts is attached
Regards,
March 15, 2019 at 5:01 am
SSIS can create its own system logging tableselect * from dbo.sysssislog
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply