Earlier this year I wrote one of my most popular blog posts to date, with a query to help harvest optimizer stats detail from plan XML when trace flag 8666 is enabled. In that blog post I hinted it would be more straightforward to harvest this type of information from plan XML after SQL Server 2016 SP2, when the default cardinality estimator includes optimizer stats details in plan XML by default and trace flag 8666 is no longer needed.
That blog post for the legacy CE is here...
Harvesting SQL Server optimizer stats detail from Query Plan XML: Part I Trace Flag 8666
Finally got around to typing up the simpler query which can be used after SQL Server 2016 SP2 with the default CE.
Faster, more efficient. Put the plan_id and plan XML for the desired set into a temp table, and have at it :-)
This allows for lots of fun possibilities - tracking updates to stats vs "good" and "bad" plans according to the query store, tying that information to duration of executions or to CPU time, etc.
Let me know if you devise a clever use for this 😀😀😀
Here's one application of this strategy - creating UPDATE STATISTICS... WITH STATS_STREAM statements based on a query plan to make plan investigation portable without moving all data and without a full 'dbcc clonedatabase'...
Fun with SQL Server Query Store, Query Plan 'StatisticsInfo' XML nodes, and STATS_STREAM