For each database where I enable Query Store, I’d consider the workload and then look at the settings. I tend to think that the default value of 100MB for MAX_STORAGE_SIZE_MB is really low, and I would be inclined to bump up STALE_QUERY_THRESHOLD_DAYS from 30 to something a bit higher. I’d also probably drop DATA_FLUSH_INTERVAL_SECONDS to something lower than 900 seconds (15 minutes) if my storage can support it. This setting determines how often Query Store data is flushed to disk. If it’s every 15 minutes, then I could potentially lose 15 minutes of Query Store data if my server happened to crash before it could be written to disk. I’d also think about changing INTERVAL_LENGTH_MINUTES to a value smaller than 60 if I wanted to aggregate my query data over a smaller amount of time. Sometimes interesting events happen within a 60 minute time frame, and they get can lost when data is aggregated across that window. However, aggregating more frequently means I’m adding processing overhead to the system – there’s a trade-off there to figure out.
In our environment at least, 100 MB of query store data would last, oh, a couple hours? Definitely tweak your settings and keep an eye on them early on.