Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Best way for SSIS log...there are so many Expand / Collapse
Author
Message
Posted Wednesday, May 7, 2014 7:00 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 27, 2014 12:56 PM
Points: 7, Visits: 15
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
Post #1568439
Posted Wednesday, May 7, 2014 7:21 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, July 28, 2014 8:13 AM
Points: 1,288, Visits: 1,847
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
Post #1568455
Posted Wednesday, May 7, 2014 7:41 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 27, 2014 12:56 PM
Points: 7, Visits: 15
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.
Post #1568473
Posted Wednesday, May 7, 2014 8:10 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 5:19 PM
Points: 3,374, Visits: 7,303
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.
I am a great believer in luck, and I find the harder I work the more I have of it. Stephen Leacock

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1568492
Posted Wednesday, May 7, 2014 8:24 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 27, 2014 12:56 PM
Points: 7, Visits: 15
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.
Post #1568500
Posted Wednesday, May 7, 2014 8:37 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Yesterday @ 3:47 PM
Points: 843, Visits: 2,324
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
PS C:\>(Find-Me).TwitterURL
@wsmelton
PS C:\>(Find-Me).BlogURL
meltondba.wordpress.com
Post #1568507
Posted Wednesday, May 7, 2014 8:39 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Yesterday @ 11:29 AM
Points: 4,986, Visits: 11,685
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.



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.
Post #1568509
Posted Wednesday, May 7, 2014 9:08 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 27, 2014 12:56 PM
Points: 7, Visits: 15
I am sorry again...it is not my intention to insult anyone.

I updated my original question based on the input I got.
Post #1568524
Posted Wednesday, May 7, 2014 9:20 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 27, 2014 12:56 PM
Points: 7, Visits: 15
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
Post #1568536
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse