What are the challenges you face when working across database platforms? Take the survey

How to identify the user that ran a Query

Ensors_BHEnsors_BH Posts: 2 New member
edited August 26, 2020 2:00PM in Redgate Monitor
We have an issue occasionally where a large query is run on our application, which can use 100% of CPU on the server for an extended period, and we would like to be able to identify the user that started the query so we can better troubleshoot what causes the issue. Is this possible from SQL Monitor? We can easily see the top queries, but i cannot see how to identify the user that started the query.

Best Answer


  • Options
    jmillarjmillar Posts: 2 New member
    I ran into exactly the same situation today -- curious about any feedback.
  • Options
    Alex BAlex B Posts: 1,146 Diamond 4
    The top queries is a cumulative metric (i.e. it shows totals or average per execution rather than specific runs). 

    If you click into a query and there was a specific wait associated with the query that will show the login that experienced the wait - or if you had an alert for blocking process or long-running query then it would give more details on a specific query including the user involved.
    Product Support Engineer | Redgate Software

    Have you visited our Help Center?
  • Options
    Ensors_BHEnsors_BH Posts: 2 New member
    Hi Alex, that's great, thank you. I'm running 10.0.8 at the moment so I will get our monitor installation updated.
Sign In or Register to comment.