Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Don't break because the schema changes; if it changes in a breaking way, we'll know anyway #76
Per "The 'SecurityPolicyApplied' attribute is not declared", almost every time SQL Server gets updated there are attributes added to the execution plan schema, which breaks the schema validation done while processing the execution plan if no one remembers to update the XSD in DataExplorer.
But there's really no reason to do a schema validation in the first place, since we can generally trust that SQL Server will return a conformant execution plan XML, and if there are breaking changes we'll know because the execution plans will stop displaying correctly—more informative and less likely than the current behaviour of breaking because of stuff we don't even care about.