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.
Bob Vale shared this idea
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.