May 16, 2018 at 10:20 pm
We use sqldiag in our environment to collect the information for later troubleshooting purpose when required. We have sufficient filter applied so there is no concern for performance impacting. Also, we have configured the monitoring to capture and notify any long running query which is taking more than 30 seconds so that we can tweak the query further.
One of the queries which came lastly in this "long running query" alert is from sqldiag.
It's mainly to collect the io stats for which its fn_virtualfilestats but the parameter value @DatabaseId shows as -1 and the query were running for 182 mins before it gets completed. We don't kill these queries as they are non-performance impacting.
Would like to know if anyone experiences this with sqldiag and have any thought to share, will be helpful.
I have attached the session detail which i captured using "long running monitor"
Thanks,
Ashish
----------
Ashish
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply