SQL Prompt 9 suggestions

chrisleonard

Hey folks,

I have a couple of observations about SQL Prompt 9. First, and I'm sure you are working on this already, we need to be able to control whether the "bad smells"/linting feature is on or off, and we need to be able to pick individual rules to be shut down. The reason for this is that if you have a very sizable body of code that makes the linter light up, you may know that code is OK "given the circumstances." However, this means that the linter is underlining tons of stuff it should not, and it hurts the signal-to-noise ratio. I think it would be good to allow us to make this feedback less noisy so that we can pay attention to the recommendations that actually matter to us in our particular jobs.

Second, In the SQL Prompt Options, under Format > Styles, there is an option to "Apply column alias style." The choices that have quotation marks appear to only use apostrophes (inverted commas). I believe that the ANSI standard states that object names can be delimited by double-quotes - and an alias is parsed as an object name, so those options should show double-quotes. The only standard use of apostrophes is to delimit literal strings. I think that we should align with ANSI standards where we can, even though SQL Server allow variants like 'identifier' and [identifier].

Just food for thought - thanks!

Cheers,
Chris Leonard
GoDaddy, FoRG

Michael Clark

Hi @chrisleonard,

Thanks for getting in touch and for the detailed feedback, much appreciated.

It is currently possible to enable/disable code analysis via the top level menu "Enable Code Analysis" in SSMS. You can also enable/disable individual rules via the "Manage Code Analysis Rules..." or inspection sidebar. Does that solve your issue or is there some additional you would like to configure the signal to noise ratio?

With your second idea around having ANSI standard column alias styles, would it be possible to submit it to our UserVoice forum? Then we can gauge the level of interest from the community and collect additional information.

Best,
Michael

chrisleonard

Sorry for the delay. Thanks for getting back to me, and yes, I will go over to the UserVoice forum right now to float the idea there.

Cheers,
Chris Leonard
FoRG, GoDaddy

philljones22

That's great to hear! It sounds like the current options for enabling/disabling code analysis in SSMS (top menu and rule management) already address the core functionality I was looking for.  

While those features are helpful, it would be fantastic if there were ways to further refine the signal-to-noise ratio of code analysis messages.  Perhaps future options could include:

* **Severity Levels:**  The ability to filter or prioritize code analysis messages by severity (e.g., critical, warning, informational)  could help focus on the most important issues.

* **Contextual Suppression:**  A way to suppress specific code analysis messages for certain contexts or code blocks could be useful to avoid getting flooded with messages for known edge cases.

These are just a few ideas, but I'm sure there are other ways to improve the usability of code analysis tools.

On the ANSI standard column alias idea, submitting it to your UserVoice forum sounds perfect.  That way, the community can weigh in and see if there's broader interest.  I'll be happy to submit it there to gauge user sentiment.

Thanks for listening to the feedback – it's much appreciated! Visit Cava Huntsville Menu.

kinseysmith

Peryourhealth is a user-friendly platform that allows you to pay your medical bills conveniently online, anytime, and anywhere.

kinseysmith

Suppose you face technical difficulties or encounter issues with the MyLowesLife portal. In that case, you can clear your browser cache and cookies using a different browser or device or contact the MyLowesLife support team for assistance.