Another post for me that is simple and hopefully serves as an example for people trying to get blogging as #SQLNewBloggers.
I never knew I could change case for objects in SSMS easily. This actually was something that another individual pointed out to me, but once I tried it, I liked it and know I’ll use it at times.
CTRL+Shift+L will lowercase whatever text is selected in SSMS. A quick gif to show this below, where I select a portion of the code and then CTRL+Shift+U to upper case it, which is what I’d want. I then CTRL+Shift+L to put it back.
Normally I use SQL Prompt to do these types of things, but that reformats the entire section of code. I don’t always want to do that. I could certainly CTRL+K, Y, which would upper case this according to my current format, but I can’t change to lower case easily. Knowing these shortcuts makes it easy for me to match case if needed.
SQLNewBlogger
When I ran across this and realized it was new, I just wrote this post. It took about 5 minutes and I spent more time deciding if I should record the screen than it took to just do it.
You could easily write this type of post as you learn small things. Tag them with SQLNewBlogger as well to encourage others.
Voice of the DBA 
This method of changing case in SSMS isn’t new. It’s always been that way even prior to when they started screwing up SSMS in version 17. 😀
What is new is that Copy’n’Paste from a code window in SSMS is no longer WYSIWYG like it used to be prior to SSMS 17. There is some little bit of respit in that they created a new category for fonts under “Print and Copy/Paste” but it doesn’t cover everything and it shouldn’t be necessary. Copy and paste should be WYSIWYG but they messed that up when they came out with 17 and it still hasn’t been fixed.
I’ve also given up trying to help MS by reporting errors because they keep playing musical-sites and it doesn’t seem to accomplish anything much unless it’s a total showstopper or “good for marketing”. In this area, I’m really disappointed in MS. First, they broke what used to be and they don’t appear to fix things they broke. Forget new features like the 12 year old suggestion about having a high speed sequence generator that Erland Sommarskog proposes and that many of us have railed for. According to the MS comments on that one, they can’t even understand why anyone would need to use such a thing (Tally function, etc).
I continue to be disheartened by “new/improved” functionality changes… STRING_SPLIT() is a primary example. I find it difficult to believe that supposed knowledgeable people would even consider releasing such a thing without an ordinal position of the returned elements and then taking a whopping almost 6 years to get around to fixing such a thing.
And, don’t get me started on what MS calls “documentation”. Quality/accuracy there continues its long plummet that started ever since they stopped installing BOL as a part of SQL Server.
I’d write an article about it but it would just annoy people that don’t get it rather than motivating them. I AM going to try to submit some changes about how REORGANIZE is documented and several spots where they still say that GUIDs are bad due to fragmentation. What a misleading mistake that and index maintenance recommendations have been for more than 2 decades. Even I drank their Purple Kool-aid as a younger man. 😦
LikeLike
Pingback: Changing Case in SSMS – Curated SQL