Long Running Query

• 
  Hi - and thanks for trying the beta.
  
  SQL Response should be capturing the SQL already. If you bring up the incident and click on the process in the list in the details pane then the SQL Query Fragment should show the SQL that was running.

  Nigel Morse February 07, 2008 08:54

  - 0 +
• 
  In every case so far that pane is empty.

  Giggles220 February 07, 2008 08:55

  - 0 +
• 
  Hi - I've sent you a pm about this - thanks.

  Nigel Morse February 07, 2008 09:18

  - 0 +
• 
  It would also be nice if in addition to start/end time, if there was a duration column so you don't have to do the math...

  philcruz February 13, 2008 13:21

  - 0 +
• 
  It would also help if the session's prepared SQL were divulged, not just the sql as in:

  Custom_IndividualSearch;1
  

  which doesn't tell me what the parameters were, so I can't reproduce it...
  
  And there's no "End Time" because it's a ".Net SqlClientDataProvider" session...
  
  Thanks.

  PDinCA February 13, 2008 17:12

  - 0 +
• 

  PDinCA wrote:

  It would also help if the session's prepared SQL were divulged, not just the sql as in:

  Custom_IndividualSearch;1
  

  which doesn't tell me what the parameters were, so I can't reproduce it..

  
  The SQL text is what we get out of the SQL server's input buffer (on SQL 2000) or from the DMV sys.dm_exec_sql_text on 2005. If it's a persistant problem then you can put the server in the highest level and collect trace data as well which should then capture the profiler output (but be aware this obviously has more impact on your server)

  Nigel Morse February 15, 2008 10:12

  - 0 +
• 
  If the query belongs to a Job and we know full well that the job will last, say up to minute, how can we configure SQL Response to "Ignore Long Running Query on <this> Job"?
  
  If it's not a current option request, please consider this an enhancement request.
  
  We, as users, need far greater granularity over what we regularly ignore so we can see the true incidents. Server-level and Incident Type are far too high level. With the thousands of incidents over three days on one Production server and three development boxes, I'm overwhelmed... and with no DBA position folks in small shops like me and other posters need all the help we can get to focus us on the truly important issues...
  
  Thanks for your consideration.

  PDinCA February 15, 2008 12:36

  - 0 +
• 
  Also, if the process happens to be "Red Gate SQL Response" can you give us the option to ignore it, please? After all, there's not much we can do about it... :lol:

  PDinCA February 15, 2008 15:56

  - 0 +
• 

  PDinCA wrote:

  Also, if the process happens to be "Red Gate SQL Response" can you give us the option to ignore it, please? After all, there's not much we can do about it... :lol:

  
  No... but we might be able to! Could you post the SQL that we display and I can then match it to what we're doing at the time and try to optimize it. I'd rather we didn't run any long running quieries rather than just mask them from you.

  Nigel Morse February 18, 2008 07:27

  - 0 +
• 

  select GETDATE(); DBCC SHOWCONTIG WITH TABLERESULTS, ALL_INDEXES, FAST
  

  PDinCA February 18, 2008 12:26

  - 0 +

Add comment

Please sign in to leave a comment.