|
|
|
Grasshopper
 
Group: General Forum Members
Last Login: Friday, March 12, 2010 3:05 AM
Points: 14,
Visits: 95
|
|
|
|
|
|
SSC Veteran
Group: General Forum Members
Last Login: Wednesday, March 10, 2010 2:55 AM
Points: 272,
Visits: 1,367
|
|
|
|
|
|
Forum Newbie
Group: General Forum Members
Last Login: Tuesday, March 02, 2010 12:44 PM
Points: 2,
Visits: 5
|
|
| Is there a particular reason you don't use the built-in logging?
|
|
|
|
|
Grasshopper
Group: General Forum Members
Last Login: Friday, March 12, 2010 3:05 AM
Points: 14,
Visits: 95
|
|
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
|
|
|
|
|
Forum Newbie
Group: General Forum Members
Last Login: Wednesday, August 05, 2009 1:50 PM
Points: 2,
Visits: 7
|
|
| Hi Arun, Following your steps exactly as provided doesn't work. The Expressions Editor Query produces a cannot be parsed error message.
|
|
|
|
|
Grasshopper
Group: General Forum Members
Last Login: Friday, March 12, 2010 3:05 AM
Points: 14,
Visits: 95
|
|
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
|
|
|
|
|
Forum Newbie
Group: General Forum Members
Last Login: Wednesday, August 05, 2009 1:50 PM
Points: 2,
Visits: 7
|
|
| 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!
|
|
|
|
|
SSChampion
Group: General Forum Members
Last Login: Yesterday @ 10:43 PM
Points: 20,100,
Visits: 13,650
|
|
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, 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/
|
|
|
|
|
Grasshopper
Group: General Forum Members
Last Login: Friday, March 12, 2010 3:05 AM
Points: 14,
Visits: 95
|
|
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
|
|
|
|
|
Forum Newbie
Group: General Forum Members
Last Login: Monday, February 15, 2010 9:52 AM
Points: 2,
Visits: 129
|
|
| Is it possible to add Cointainer Name along with Package Name & Task Name. I think its little bit tircky
|
|
|
|
