Comments
Sort by recent activity
I believe you need to remember to click on the ‘Save and Restart’ button after you uncheck the boxes. [image] / comments
I believe you need to remember to click on the ‘Save and Restart’ button after you uncheck the boxes.
Glad to be able to help… but make no mistake this is a bit of a tortured process. But you did it right. Side by side install. Uninstall SQL Prompt. Re-install SQL Prompt. Do the crazy stuff and voila…. things ‘should’ work. Nothing wrong will having two SSMS versions installed especially if one is the new SSMS 21. As the release notes stated… SQL Server Management Studio (SSMS) 21 is now generally available (GA) | Microsoft Community Hub “We made the difficult decision to hold back SQL Server Integration Services (SSIS) support for this release.” So what this means is.. 21 doesn't really have full functionality and having another SSMS installed is good to fill in those gaps and also in case the new SSMS 21 starts acting fussy. I've noted some issues with SSMS 21 already and submitted my findings. SSMS 21 is great leap forward.. but it's still new, so I am proceeding with caution. Now throw SQL Prompt on top of that and you never know what could happen. Always have a back-out and a back-up plan. / comments
Glad to be able to help… but make no mistake this is a bit of a tortured process.But you did it right. Side by side install. Uninstall SQL Prompt. Re-install SQL Prompt. Do the crazy stuff and ...
After installing latest SQL Prompt don't forget to do all the other ‘crazy’ stuff..
Extensions | Customize Menus…
Uncheck both SQL Prompt boxes
Close SSMS
Open SSMS | Extensions | Customize Menus
Check second SQL Prompt box
Restart SSMS
That should make the SQL Prompt menu appear in SSMS. / comments
After installing latest SQL Prompt don't forget to do all the other ‘crazy’ stuff..
Extensions | Customize Menus…
Uncheck both SQL Prompt boxes
Close SSMS
Open SSMS | Extensions | Customize Menus
C...
Just to clarify… you don't uninstall SSMS.. You uninstall and then re-install SQL Prompt… / comments
Just to clarify… you don't uninstall SSMS.. You uninstall and then re-install SQL Prompt…
Yes.. I hear you. I don't like this process either. The problem seems to be that if you install a brand new version of SSMS (SMS 21 GA) side by side with an existing version of SMSS (e.g. v20) that has SQL Prompt installed and working (and licensed), and then you do an upgrade of SQL Prompt, it doesn't install SQL Prompt into the new SMSS you just installed (e.g. the one that doesn't have SQL Prompt). It upgrades the SQL Prompt in your previously existing SMSS but not the new one (in this case the SSMS 21 GA). That's why you have to uninstall SQL Prompt. (ugh!!) Lately, SQL Prompt only seems to ‘find’ SSMS versions on a fresh install.. not an upgrade. As a rule, I do not like un-installing SQL Prompt. I got burned one time where it lost all my history and settings. I've done the uninstall / re-install a few times but always cross my fingers. I just wish the ‘upgrade’ would find any new SSMS instances (that don't have SQL Prompt) and just install it. You're already licensed on the machine.. just install it. / comments
Yes.. I hear you. I don't like this process either. The problem seems to be that if you install a brand new version of SSMS (SMS 21 GA) side by side with an existing version of SMSS (e.g. v20) that...
Well believe it or not, that makes me feel better… knowing that it's likely not a ‘just me’ thing. I understand how Redgate cannot yet commit to ‘full’ SSMS 21 support (SSMS 21 is still in preview after all) so it could be a combination of things between SSMS 21 and SQL Prompt. Hopefully they will investigate this soon. / comments
Well believe it or not, that makes me feel better… knowing that it's likely not a ‘just me’ thing. I understand how Redgate cannot yet commit to ‘full’ SSMS 21 support (SSMS 21 is still in previe...