Best way for SSIS log...there are so many

  • Hi,

    Everywhere somebody talks about logging a different way in SSIS packages. What is the best way to log the trace and errors. I am confused and not sure how much I can rely on SSIS db logging

    Updating the original question based on the input I got.

    I read articles and books that talk about logging and confused totally.

    In some of those articles and books they talked about some custom logging and logging based on SSIS events.

    I did download and setup the SSISreporting pack that runs on SSISDB. But a job failed and there is no log in the SSISDB. Also I noticed this only works if we deploy the packages to the SSISDB. I am not sure if the logging based on SSIS events adds any value compared to the SSIS DB logging. So, I am lost among the options.

    I was wondering if somebody has any recommended way to do the logging in Sql Server 2012.

    Also I am planning to log it to a sql server database as a destination.

    Thank you

  • vanamali (5/7/2014)


    Hi,

    Everywhere somebody talks about logging a different way in SSIS packages. What is the best way to log the trace and errors. I am confused and not sure how much I can rely on SSIS db logging

    Thank you

    Setup different types of logging available from SSIS and see which one makes the best sense for your requirements.

    Alex S
  • I am sorry...is that really an answer?

    It takes lot of time and effort. I was asking that question to see what others have done.

  • vanamali (5/7/2014)


    I am sorry...is that really an answer? Congratulations you just added a new post to your 'post count'.

    It takes lot of time and effort. I was asking that question to see what others have done.

    That might be an answer considering the lack of details of your post.

    There's rarely one solution that fits on every environment. Some people might want a detailed log, while others might use minimum logging.

    I don't have much experience with SSIS logging, but with more details on what you need, someone can give a better answer.

    Luis C.
    General Disclaimer:
    Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

    How to post data/code on a forum to get the best help: Option 1 / Option 2
  • People who can answer my question can understand it. If you don't know anything about it why do you respond? I am sorry, I am not trying to be rude. But, it does not make any sense to me.

    Responses like these decrease the quality of these forums.

    Anyways

    I am looking for a logging solution for my SSIS packages.

    Microsoft gave several solutions including the recent SQL Server 2012 SSISDB logging. I am hoping to find some guidance on what is the best way or combination of solutions to be able to troubleshoot the issues with the SSIS packages.

  • vanamali (5/7/2014)


    Hi,

    Everywhere somebody talks about logging a different way in SSIS packages. What is the best way to log the trace and errors. I am confused and not sure how much I can rely on SSIS db logging

    Thank you

    Are you aware of what methods are available for logging? They all can log the same type of information is a matter of choosing which destination you want for that information.

    There is no "best method" but the most common method used is the SQL Server log provider. It offers up different ways to analyze your package execution times; there are some canned reports for SSRS that are available from Microsoft that can report on this same information.

    Shawn Melton
    Twitter: @wsmelton
    Blog: wsmelton.github.com
    Github: wsmelton

  • vanamali (5/7/2014)


    People who can answer my question can understand it. If you don't know anything about it why do you respond? I am sorry, I am not trying to be rude. But, it does not make any sense to me.

    Responses like these decrease the quality of these forums.

    Anyways

    I am looking for a logging solution for my SSIS packages.

    Microsoft gave several solutions including the recent SQL Server 2012 SSISDB logging. I am hoping to find some guidance on what is the best way or combination of solutions to be able to troubleshoot the issues with the SSIS packages.

    With this sort of attitude you will get fewer answers, I guarantee it. In this case, what is best for me may not be best for you, hence the follow-up questions.

    I know plenty about it, before you insult me as well.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • I am sorry again...it is not my intention to insult anyone.

    I updated my original question based on the input I got.

  • Shawn Melton (5/7/2014)


    vanamali (5/7/2014)


    Hi,

    Everywhere somebody talks about logging a different way in SSIS packages. What is the best way to log the trace and errors. I am confused and not sure how much I can rely on SSIS db logging

    Thank you

    Are you aware of what methods are available for logging? They all can log the same type of information is a matter of choosing which destination you want for that information.

    There is no "best method" but the most common method used is the SQL Server log provider. It offers up different ways to analyze your package execution times; there are some canned reports for SSRS that are available from Microsoft that can report on this same information.

    Thank you Shawn for the useful links. I did not know there were reports on the Execution logs. Regards

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

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