7

Requesting an execution plan from SEDE on any query currently seems to always return the message:

The 'SecurityPolicyApplied' attribute is not declared

Improve this question
1
  • 5
    Ughhh, this is the most annoying thing. Let me see if there's any reason to even do the operation that causes this
    – Tim Stone
    Apr 19, 2016 at 13:05

1 Answer 1

Reset to default
4

Right, so Data Explorer was upgraded to SQL Server 2016 last night, and as usually happens there were additional attributes added to the execution plan XML to expose information about new features, etc.

Since we were doing schema validation on this XML with the strict schema provided with SQL Server, it complained because no one updated the schema to the newest version. This happens pretty much every time there's an upgrade, and it's a pain because there's not really any value to doing the schema validation to begin with. So now we won't, pending a pull/redeploy.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .