Red Gate forums :: View topic - How to read Trace Information
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Monitor 3
SQL Monitor 3 forum

How to read Trace Information

Search in SQL Monitor 3 forum
Post new topic   Reply to topic
Jump to:  
Author Message
m.cecili



Joined: 26 Apr 2012
Posts: 2

PostPosted: Fri Apr 27, 2012 9:00 am    Post subject: How to read Trace Information Reply with quote

I tried to activate Trace to have more information about deadlocks.
I need an explanation how to read extra information.
I saw that in Trace tabsheet now i can click every single process row and read other information about the executed sql.
My problem was that the basic information about deadlock, more exatly the line of code that generated dead lock, was wrong.
We use a lot of stored procedure very long that call other stored procedure and is difficult to understand which line of code causes the problem.
I hoped that enabling trace, it could help me to understand but i don't know how to read all logged information. Can you help me?
Back to top
View user's profile Send private message
m.cecili



Joined: 26 Apr 2012
Posts: 2

PostPosted: Fri Apr 27, 2012 11:29 am    Post subject: Reply with quote

When i enable trace the informations are not immediatly available. I saw an information tip which say: NO SQL statements to display. No statement captured for the selected process...
After how many time trace information are displayed? Is there a fixed rule?
Back to top
View user's profile Send private message
Chris Spencer



Joined: 29 Aug 2006
Posts: 301
Location: Red Gate - Cambridge

PostPosted: Mon Apr 30, 2012 12:42 pm    Post subject: Reply with quote

On activating trace in SQL Monitor we immediately set trace running on the relevant monitored server. When an alert is raised that supports trace (going from memory this would be Deadlocks, Long-running Query, Job Failed, Blocked Process and Error Log entries), we read the trace files and transfer data for the relevent process and time period into our data repository. The recently raised alert should display this trace data although not always straight away. If there's a lot of trace data in the time period that the alert was raised it takes a while to transfer so there could potentially be a couple of minutes lag before the trace data appears. I believe that you'd need to reopen the alert to get the trace to appear.

So do you see the call to the stored procedure but not the code in the stored procedure itself?

Regards
Chris
_________________
Chris Spencer
Test Engineer
Red Gate
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group