Post reply

An Introduction to Integration Services log providers

  • December 28, 2011 at 10:36 pm

    #391221

    Comments posted to this topic are about the item An Introduction to Integration Services log providers

  • December 28, 2011 at 10:37 pm

    #1426321

    Good intro about logging in SSIS. Keep them coming. Your articles are very good for beginners like me in SSIS.

    Thanks.

  • December 29, 2011 at 1:47 pm

    #1426695

    For more information about events logged by SSIS packages the Integration Services Service, see these BOL topics, Understanding Events Logged by an Integration Services Package, Understanding Events Logged by the Integration Services Service

    You can use the SSIS Log Analyzer to analyze complex and verbose SSIS logs. For a demo, see the SSIS Log Analyzer (SQL Server Video).

  • December 29, 2011 at 1:58 pm

    #1426703

    Thanks!

  • December 30, 2011 at 10:07 am

    #1427061

    I have always been using either SQL Server or text file logging with SSIS, since they are easy to review. Could you comment on potential usages (advantages/disadvantages) of some of the other types of logging, which seem a bit more "exotic", such as trace file or XML?

    Thank you for the article!

  • December 30, 2011 at 10:36 am

    #1427069

    I decided to explore SSIS logging because I wanted to be able to insert custom data into the logging stream, specifically the date/time stamp of data files processed by SSIS packages.

    One of the criticisms that I had received from my previous article

    Copy-and-Paste SSIS Execution Monitoring with Failure-Alert Email[/url]

    was that SSIS logging provided everything already and I should learn it rather than reinvent the wheel.

    All five of the SSIS logging outputs contain the same exact data. My guess is that there are custom clients that can read and display each type of log output. For all practical purposes it doesn't matter which one you use. The text file is the easiest to use because you can just open it in notepad. Another approach would be to write an SSRS report to view the sys.sysssislog table.

    I still don't think you can store the file timestamp in the SSIS logging stream, which is very useful information if there is a possibility that your job might reprocess a file from the previous day if a new one hasn't replaced it.

  • January 5, 2012 at 1:33 pm

    #1429338

    will this run when a SSIS package runs as a job?

    at the start of every year i try to increase the amount of logging and reporting we have to make life easier

  • January 5, 2012 at 1:54 pm

    #1429350

    The whole idea is that the logging occurs whenever the package runs.

    The only catch is you have to add logging to each SSIS package individually.

    Only the packages that you have added it to will log their execution.

    Crazy, I know, but that goes along with the fact that you can't write global functions that all your SSIS packages can use.

    Each of your SSIS packages is an island unto itself.

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply