January 20, 2006 at 2:04 pm
In SQL 2000 you could view job history and look at step 1-x to get more detail on what happened. How or where do you do this in SQL 2005. Yes I can see history but I'm trying to find more info on why a job failed. Any hints?
Peter Cwik
January 23, 2006 at 8:00 am
This was removed by the editor as SPAM
January 24, 2006 at 4:47 pm
Did you go into Management Studio's Object Explorer and check the Error Logs under SQL Server Agent? Also, did you try utilizing the Job Activity Monitor?
All the best,
Dale
Author: An Introduction to SQL Server 2005 Management Studio
January 24, 2006 at 5:04 pm
Yes, I looked in those places and its still not as much information that was available in 2000.
January 24, 2006 at 5:30 pm
A couple of things you might want to consider:
Understand that both of these options will cause your error log to fill up faster. You should turn off "Execution Traces" when your not troubleshooting a problem (strictly for debugging). Otherwise, it could actually impact when you are trying to troubleshoot problems down the road.
All the best,
Dale
Author: An Introduction to SQL Server 2005 Management Studio
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply