February 8, 2021 at 6:00 pm
Hello,
Hoping someone may know the answer to this one... I work on two different SSMS, one is local on my machine (v17.6), another is on a server (v18.4). My local SSMS has this nifty little feature that when I'm writing a stored proc and creating temp tables, when I type DROP TABLE at the end it will show intellisense(?) for each of the temp tables that I've created in the script above (so I don't have to go searching through to find all the temp tables). All I have to do is type # and it shows the list of temp tables. The version of SSMS on the server does not do this for me. Is there a property/setting I need to enable to allow this? It's really useful.
Thanks
February 8, 2021 at 6:38 pm
A lot of things have changed in SSMS since it became a separate product and they continue to "ditz" with it and, so far, a lot of it has been, IMHO, "negative" changes where old but nice features are going away one by one. For example, I like to "color" all constants, whether they be strings or numbers, the same color Red. That works just fine in SSMS but now when you copy code from SSMS to Word or PowerPoint (which I do a lot), the correct colors no longer "travel" with the copy and paste.
It's frustrating as hell but we're at the whims of others and I've given up on suggestions and fault reporting to the various Microsoft teams. After all, we ARE talking about the people that removed SQL Diagrams (and thankfully put back), the DEBUG feature (which a lot of other people depended on), people that thought a string splitter with no element ordinal, thought FORMAT would be a good addition even though they apparently never thought to test it for performance, though EOMonth would be useful but not SOMonth, etc, etc, ad infinitum.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2021 at 8:30 pm
So it sounds like I'm just SOL. That's a bummer.
Thanks
February 8, 2021 at 9:10 pm
Hello,
Hoping someone may know the answer to this one... I work on two different SSMS, one is local on my machine (v17.6), another is on a server (v18.4). My local SSMS has this nifty little feature that when I'm writing a stored proc and creating temp tables, when I type DROP TABLE at the end it will show intellisense(?) for each of the temp tables that I've created in the script above (so I don't have to go searching through to find all the temp tables). All I have to do is type # and it shows the list of temp tables. The version of SSMS on the server does not do this for me. Is there a property/setting I need to enable to allow this? It's really useful.
Thanks
Yes, it's under settings in SSMS.
Why is there a need to work directly on the server?
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
February 8, 2021 at 9:16 pm
Michael - On the server question, that's the only way I'm able to access the different databases in different locations. It's a centralized access point.
If this is in Settings, do you have any insight on what it's called/where it's located?
February 8, 2021 at 9:23 pm
Never mind! I found it!
In Options/Text Editor/Transact-SQL/Auto List Members.
Man, I'm glad it was just a setting here.
Thanks!
February 8, 2021 at 10:02 pm
Cool. Thanks for the feedback. Funny setting name, though. I would never have thought to look under "Auto List Members". Members aren't Objects. Gotta love the lingo. 😀
That might also be why any code I'm developing lately can't find temp tables created by the same code add, instead, underlines them as "Not found" even when I do {Ctrl-Shift-R} to refresh. Like I said, thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 9, 2021 at 3:53 am
I just checked my system. That setting is on and, apparently, defaults to being on.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 9, 2021 at 6:23 am
This was removed by the editor as SPAM
February 9, 2021 at 9:21 am
This was removed by the editor as SPAM
February 9, 2021 at 12:13 pm
Yes, I work for them. Doesn't mean I'm not right.
SSMS Intellisense is weak, at best. Check out Redgate SQL Prompt. Not just wildly superior Intellisense, but code formatting, refactoring, code analysis, snippets & more.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 18, 2021 at 10:53 am
This was removed by the editor as SPAM
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply