2

I've recently inherited a SQL Server 2017 instance with performance issues and I've been able to remediate the low hanging fruit. However, one substantial wait still remains.

The Query Store - qds_async_queue seems to be significantly high. But I'm unable to find any meaningful documentation or insight. Microsoft's online description has been at 'TDB' since SQL 2016.

Does anyone have any insight or helpful information about this wait?

Improve this question
2
  • what is experiencing this wait? user queries?
    – Martin Smith
    Feb 6, 2019 at 22:07
  • @MartinSmith this is based entirely off of performance reports. So it's the cumulative wait(s).
    – Steve
    Feb 6, 2019 at 22:15

1 Answer 1

Reset to default
3
  1. Please note that the official documentation is the official source of information.
  2. I took a brief look and this shouldn't be taken as an extreme look from every possible angle.

The wait type is benign as it's a permanent task that which is persisting QDS data in the background. The wait shows up and is incurred while the instance is up and running, it will have more incurred wait if there are items to persist and lower if there are less items to persist.

So, overall, unless there are other issues going on, this wait type can be ignored.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.