Detect the database compatibility version
When using SQL server 2016 with a database that has it's compatibility level set to 2012, I'm still being offered auto complete options for 2016 features. e.g. string_split
SQL Prompt needs to detect the database compatibility level and adjust it's intellisense accordingly.
2
votes
![](https://secure.gravatar.com/avatar/c1a80b1b926d6b2fef43ec0ba72e2d46?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
-
Chris Ford commented
This would be a godsend for admins like myself who support Azure as well as SQL versions back to 2008 all from the same copy of SSMS r17.
Its all very well flagging old-style code, but commands unsupported in the current database compatibility level are easily missed and cause bigger problems.