Josh,
So you're needing to custom log errors in SSIS, and naturally you seek to utilize the "OnError" event handler. You don't want to have to implement an event handler on each task, so you create one at the package level. You place an "Execute SQL Task" in the event handler and set it up to log the error. Great!
You then test with an error, and the event handler runs, but when you go to check the custom log in SQL Server, you see multiple entries for the same error! There has to be a way to ensure only one error gets logged...
Josh, you learned something cool or figured something difficult out relating to BI/SQL/C#/Programming/Etc. Therefore write it down here for easy recall!!!
Showing posts with label ssis. Show all posts
Showing posts with label ssis. Show all posts
Friday, July 27, 2018
Friday, February 13, 2015
Automated DB Source Control (2 of 5): The SSIS Package
Josh,
To continue from the last post, you'll need an SSIS package to drive the process. This package joins all the steps, running the custom code, the SQL Scripts, and Checking In the changes. Here's what you came up with...
Labels:
c#,
integrations,
mssql,
ssis,
tools,
visual studio online
Thursday, August 7, 2014
Using Custom DLL's in an SSIS Script Task
Josh,
So you've created an awesome class library you want to use in an SSIS package. Instead of worrying about registering it in the GAC, you can do the following to make sure your code will work in production.
So you've created an awesome class library you want to use in an SSIS package. Instead of worrying about registering it in the GAC, you can do the following to make sure your code will work in production.
Subscribe to:
Posts (Atom)