Home Dashboard Directory Help
Search

Remove Brackets from SSMS script generation by Codestr


Status: 

Active


2
2
Sign in
to vote
Type: Suggestion
ID: 837253
Opened: 3/20/2014 4:39:53 AM
Access Restriction: Public
0
Workaround(s)
view

Description

I won’t argue technical merits and I doubt this will sway the 800 lb. gorilla. But all one need do is listen to the chatter on the internet to realize that the use of brackets in SSMS script generation is a royal PIA. I respectfully request an option to remove them in SSMS. At the end of the day, you know this can be done and it would make a whole lot of of MSFT customers happy. Thank you.
Details
Sign in to post a comment.
Posted by Microsoft on 6/2/2014 at 1:42 PM
Hi,

Thank you for the suggestion and the discussion.
Unfortunately, after a few internal discussions we realised that we will not be able to take this suggestion for the next release. We might reconsider it for one of the future releases.

Thank you again for your feedback. We appreciate your time and feedback is really helping us defining the product.

Evgeny Krivosheev
SQL Server Program Manager
Posted by Scott R. 007 on 3/30/2014 at 12:22 AM
Building on this request, the requested SSMS option should be to conditionally generate brackets where needed (to properly delimit generated object name references which have embedded characters that require brackets - such as spaces), and not generate brackets for object name references that do not require brackets. The T-SQL syntax rules for conditions requiring brackets are well documented and understood - no ambiguities here.

In other words, I don't want generated SQL DDL / DML to fail when no brackets are used but some brackets are needed.

Perhaps this is what the author meant when requesting "remove the use of brackets" - conditionally generate brackets only where required, and avoid blind use of generated "brackets everywhere" and "brackets nowhere". I didn't get the "conditional" part from my read of this request, which is why I chose to respond with this amplification.

I agree that the reduced "clutter factor" would be beneficial.


Thanks,

Scott R.
Sign in to post a workaround.