April 16, 2022 at 6:28 am
I have a query I periodically run against the query store for retrieving the number of milliseconds of CPU consumed by the current database for time windows of the recent past (e.g. each 5-minute window for the past 4 hours). That's all I'm using the query store for. What are the best values to use in my ALTER DATABASE CURRENT SET QUERY_STORE statement so that 1) the query store doesn't stop gathering data if some threshold is reached (e.g. hitting a memory limit), 2) it only gathers the minimum info needed for retrieving CPU usage, and 3) if a lot of queries happen in a particular time window, the CPU usage for that time window doesn't return a lower than real value because of queries being discarded as part of automatic sized-based clean-up? Thanks.
April 17, 2022 at 7:10 am
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy