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 optimizer stats details are included in plan XML by default and trace flag 8666 is no longer needed.

That blog post 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.

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.

SELECT plan_id, CONVERT(XML, query_plan) planXML INTO ##plans FROM sys.query_store_plan; ;with XMLNAMESPACES(default 'http://schemas.microsoft.com/sqlserver/2004/07/showplan') SELECT plan_id, dbName, schemaName, tableName, statName, LastUpdate, SamplingPercent FROM ##plans CROSS APPLY planXML.nodes(N'/ShowPlanXML/BatchSequence/Batch/Statements/StmtSimple/QueryPlan/OptimizerStatsUsage') qp(qpnode) CROSS APPLY qpnode.nodes(N'StatisticsInfo') qp2(statsinfo) CROSS APPLY (SELECT qp2.statsinfo.value(N'@LastUpdate', N'varchar(max)')) LastUpdate(LastUpdate) CROSS APPLY (SELECT qp2.statsinfo.value(N'@ModificationCount', N'varchar(max)')) ModCount(ModificationCount) CROSS APPLY (SELECT qp2.statsinfo.value(N'@SamplingPercent', N'varchar(max)')) SP(SamplingPercent) CROSS APPLY (SELECT qp2.statsinfo.value(N'@Statistics', N'varchar(max)')) statName(statName) CROSS APPLY (SELECT qp2.statsinfo.value(N'@Table', N'varchar(max)')) tableName(tableName) CROSS APPLY (SELECT qp2.statsinfo.value(N'@Schema', N'varchar(max)')) schemaName(schemaName) CROSS APPLY (SELECT qp2.statsinfo.value(N'@Database', N'varchar(max)')) dbName(dbName) OPTION (MAXDOP 1);
Harvesting SQL Server optimizer stats detail from Query Plan XML: Part II SQL Se ...

Let me know if you devise a clever use for this :grinning::grinning::grinning:

本文数据库(mssql)相关术语:熊片数据库 mssql数据库 oracle数据库 pubmed数据库 access数据库 万方数据库

本文标题:Harvesting SQL Server optimizer stats detail from Query Plan XML: Part II SQL Se ...

技术大类 技术大类 | 数据库(mssql) | 评论(0) | 阅读(92)