SQL Compatibility Level

[JasonMcD (Jason McDermott)]

@TomAlexander

very fringe/obscure syntax

cough FOR XML vs. STRING_AGG cough

FOR XML PATH versus STRING_AGG

I found a resolution for this issue. You should still move to STRING_AGG as soon as you get on SQL 2017 or above. Edit the query with the issue, go to Actions\Execution Settings. In the dialog that pops up you can add a new setting called QueryOldCompanySecurity with any value (I used “True”). Make sure to set the Persist in Query flag. Hit OK, and save the query. I had a tiny bit of trouble with this UI, just don’t go back into the Query Execution Settings UI and click OK (you can click CANCEL…

Technically I wasn’t out of compliance when we got bit with that, but it was close.

And I think TRIM() is what @Mark_Wonsil is probably referring to, new for 2017.