new TRANSLATE function syntax not recognized by SSMS 17.3
The new TRANSLATE function is not recognized as valid syntax by SSMS 17.3 intellisense, though it executes just fine against SQL Server 17 instances. The TRANSLATE syntax is underlined in red with the warning "'TRANSLATE' is not a recognized built-in function name"
Tested against SQL Server 17 RTM.
Thanks for reporting the issue. We’ll look into fixing it in the next major release of SSMS.
I can confirm that this has been fixed as of SSMS v18.0 Preview 6 (SQL Server Management Studio 15.0.18075.0). Thanks!
Now please fix this one:
"IntelliSense does not recognize CATALOG_DEFAULT as a valid collation" ( https://feedback.azure.com/forums/908035-sql-server/suggestions/32897992-ssms-17-3-intellisense-does-not-recognize-catalog ) :-)
This is an issue for SSMS v18.0 Preview 5 (SQL Server Management Studio 15.0.18068.0)
Rogério Moraes de Carvalho commented
Exactly the same problem in SQL Server Management Studio v17.9.1 RTM.
Mike Williams commented
Still present in SSMS 17.7
This is still an issue in SSMS 17.5:
SELECT TRANSLATE('123', '2', 'a');
That statement works, but IntelliSense indicates that it is not a valid command.
I believe I submitted this bug, just forgot to record the MS Connect URL at the time.