Menu
There are 5 different types of logging in SSIS
I am in a production environment where developers do not have access to production systems.
Which logging method should be my poison of choice, and why?
566
Logging the execution of a package stored in the SSIS catalog couldn't be easier. The catalog has four built-in logging levels to choose from: Basic (the default), Performance, Verbose, and None. These logging level determine how much information is logged when the package is executed.
The SSIS log provider for SQL Server in SSIS Package loggingRight-click on the control flow area and go to logging again. Select SSIS Log Provider for SQL Server from the drop-down list and click Add. You can use an existing SSIS package connection or use a new connection for SQL Server.
Event Handlers are supposed to be used to handle that event i.e. not just logging information. In other words, they provide the capability of doing much more that logging. Whereas the SSIS logging just does what the name suggests.
If you're not going to have access to the production server, then SQL Server logging is your best bet by far. You'll have plenty of ways of viewing the logged information, for example via custom SSRS reports or web pages, or direct access to the tables if your DBA allows it. Also, the logs will be easier to search and filter when in a table.
82
Personally I prefer logging to SQL Server.
I think this is because it puts the data in a form which I can immediately access and process. For example, I can then slice and dice the data, export it to another server, setup agent jobs to monitor the logs and email alerts etc.
42
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
