SSMS 2016 problem showing execution plans when querying SQL 2016 SP1 - by Brent Ozar

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


145
0
Sign in
to vote
ID 3113287 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 11/27/2016 5:52:36 AM
Access Restriction Public

Description

In SQL Server Management Studio 2016 13.0.16000.28, when querying SQL Server 2016 SP1, execution plans don't always render correctly.

For example, run this query:

DBCC FREEPROCCACHE
GO
SELECT * FROM sys.databases
GO
SET DEADLOCK_PRIORITY -10
GO
SELECT 
st.text AS QueryText,
qp.query_plan AS QueryPlan
FROM sys.dm_exec_cached_plans AS cp
CROSS APPLY sys.dm_exec_query_plan(cp.plan_handle) AS qp
CROSS APPLY sys.dm_exec_sql_text(cp.plan_handle) AS st
GO

Then click on the QueryPlan column for each row returned. The SET DEADLOCK_PRIORITY renders fine, but the SELECT * FROM sys.databases renders as XML instead of a graphical plan.

This may have to do with Connect item #3113286 - the outdated showplanxml.xsd that doesn't include the new query plan operators added by SP1.
Sign in to post a comment.
Posted by Microsoft on 12/19/2016 at 8:41 AM
Yes, this should be fixed in the 16.5.1 release of SSMS (https://msdn.microsoft.com/en-us/library/mt238290.aspx). If anyone is still encountering issues after updating to that version let me know.

-Charles Gagnon (chgagnon@Microsoft.com)
Posted by geoff patterson on 12/8/2016 at 12:11 PM
Microsoft has fixed this in the 16.5.1 release of SSMS that was made available this week (https://blogs.msdn.microsoft.com/sqlreleaseservices/announcing-sql-server-management-studio-16-5-1-release/). I installed that version and confirmed the fix.