On Error () Logging by Using Event Handlers

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss content posted by Arun Mallick » On Error () Logging by Using Event Handlers

19 posts, Page 1 of 2

1 2 »»

On Error () Logging by Using Event Handlers

Rate Topic

Display Mode

Topic Options

Author

Message

mail.arun2005

Posted Friday, June 19, 2009 12:56 PM

Grasshopper

Group: General Forum Members
Last Login: Thursday, December 20, 2012 1:07 PM
Points: 15, Visits: 166

Comments posted to this topic are about the item On Error () Logging by Using Event Handlers

Post #738577

Samuel Vella

Posted Friday, June 26, 2009 3:00 AM

Old Hand

Group: General Forum Members
Last Login: Friday, May 03, 2013 2:54 AM
Points: 328, Visits: 1,848

Nice article and a good companion to Jamie Thompsons blog at conchango:
http://blogs.conchango.com/jamiethomson/archive/2005/06/11/SSIS_3A00_-Custom-Logging-Using-Event-Handlers.aspx

I see you followed the same development path as I had - generalise the error logging and then the same principle can be applied to all SSIS packages in production. This leaves you with a consistant process log table which can be used for system reporting.
Handy when you want to run a quick report in the morning to check on the status of all the overnight jobs Smile

Post #742473

loydjerry

Posted Friday, June 26, 2009 10:58 AM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, August 12, 2010 9:23 AM
Points: 2, Visits: 12

Is there a particular reason you don't use the built-in logging?

Post #742870

mail.arun2005

Posted Friday, June 26, 2009 11:13 AM

Grasshopper

Group: General Forum Members
Last Login: Thursday, December 20, 2012 1:07 PM
Points: 15, Visits: 166

It gives u more customization on logging mechanism. Here I mentioned a simple example, u can use ur own ideas for a more complex logging.

Thanks for ur comments

Post #742881

cwcridindirty

Posted Friday, June 26, 2009 11:33 AM

Forum Newbie

Group: General Forum Members
Last Login: Tuesday, December 11, 2012 12:43 PM
Points: 4, Visits: 16

Hi Arun, Following your steps exactly as provided doesn't work. The Expressions Editor Query produces a cannot be parsed error message.

Post #742889

mail.arun2005

Posted Friday, June 26, 2009 11:49 AM

Grasshopper

Group: General Forum Members
Last Login: Thursday, December 20, 2012 1:07 PM
Points: 15, Visits: 166

Hi… I checked the Expression thoroughly and it is working perfectly.
Please check the user variable, may be u didn’t created the user variable named @[User::PackageLogID].
If u have created the above variable perfectly, then please send me the detail of the error message that u got.

Thank u

Post #742899

cwcridindirty

Posted Friday, June 26, 2009 1:04 PM

Forum Newbie

Group: General Forum Members
Last Login: Tuesday, December 11, 2012 12:43 PM
Points: 4, Visits: 16

Hello Arun, brilliant! you're 100% correct. I just had to get up to speed on creating user variables. Thanks much Arun! You helped me learn something today!

Post #742936

Jeff Moden

Posted Saturday, June 27, 2009 9:12 PM

SSC-Dedicated

Group: General Forum Members
Last Login: Yesterday @ 5:33 PM
Points: 32,902, Visits: 26,783

Just a quick question... I don't see where the column called "PrcocedureName" in the error log table is either described or used in the article. Is it just an unused, mispelled artifact?

Other than that, pretty cool article on simple error logging.

--Jeff Moden

"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Post #743208

mail.arun2005

Posted Sunday, June 28, 2009 1:37 AM

Grasshopper

Group: General Forum Members
Last Login: Thursday, December 20, 2012 1:07 PM
Points: 15, Visits: 166

The column named “[PrcocedureName]” can be used to detect the procedure that causes the particular error. But I didn’t implement it in the methodology; the user can implement it in case if they are using some procedures in the ETL process. The details about implementing the same will be posted in my next article.

Thank you

Post #743221

Niraj Kotecha

Posted Sunday, June 28, 2009 2:31 AM

Forum Newbie

Group: General Forum Members
Last Login: Saturday, May 18, 2013 12:51 PM
Points: 2, Visits: 207

Is it possible to add Cointainer Name along with Package Name & Task Name. I think its little bit tircky

Post #743225

« Prev Topic | Next Topic »

19 posts, Page 1 of 2

1 2 »»

Permissions