Do you have a comment or suggestion to improve SQL Server? We’d love to hear it!

SSMS 17.3 IntelliSense validates temporary stored procedures using case-sensitive comparison even on a case-insensitive instance

Using SSMS 17.3, upon creating a temporary (local or global) stored procedure, if you reference it in anything other than the original casing, then it gets flagged as invalid with a red underline and tool-tip of "Could not find stored procedure 'name'.".

This happens regardless of whether or not the instance-level collation is case-insensitive.

Yes, I did refresh the object-name cache using Control-Shift-R.

However, if the temporary object is a table, then the validation does allow for different casing on a case-insensitive instance (which is the correct behavior).

1 vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)

We’ll send you updates on this idea

AdminMicrosoft SQL Server (Product Manager, Microsoft Azure) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base