Logging and Tracing package execution 1

[bittmapp]

I have a few questions:

1. Is there a more detailed description of a package's execution other than in the debugger? A log file?

2. Is it possible to increase the tracing verbocity of the file?

3. When several packages have been scheduled using SQL Agent, is there a way to see the progress of the SQL Agent Job as it is running?

Thanks so much in advance,

bitt

 

[mrdenny]

1. Don't know. I don't think so.

2. I don't think so (unless your SQL Commands print out information.

3. If you pull up the history of the job it will tell you what steps have completed. If you run sp_hel_job it will tell you the current step.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[Catadmin]

bittmapp,

I believe you can actually stick tasks into the IS package which record what is going on into a text file which you can later examine for a more verbose description of what happened when during your package. I haven't done it myself, but Brian Knight (the founder of PASS) indicated it could be done.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[DanEvans]

This is an old post, but I thought this link would be useful to someone. I used this methodology to implement logging using event handlers in my packages.

http://blogs.conchango.com/jamiethomson/archive/2005/06/11/1593.aspx

Thanks,
Dan