My feedback

1 result found

1. Use extended events instead of trace when trace initialized due to alert

   98 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   7 comments  ·  Suggestions  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Daniel Rothig responded

   Thanks for the suggestion – we’ll monitor how popular it gets

   An error occurred while saving the comment
   Anonymous commented  ·  Jun 2, 2011  ·  Edit…  ·  Delete…

   The GUI of SQL monitor is not easy to use as SQL Response, In SQL Response, I can easy highlight the statement in Profiler Trace, but SQL Monitor not. Also, if the statement is longer than the width of browser, the end of statement can't be displayed.

   When I troubleshoot a dead lock/ blocking issue, I need switch over 2 process in Profiler Trace, it will be great if 3.0 conatin a timeline to compare 2 statement.

   Save Submitting...
   Anonymous supported this idea  ·  Jun 2, 2011