Comments
1 comment
-
That's correct, and this is not a bug.
SQL Prompt 3 does not run as a separate process the way SQL Prompt 2 does, instead it sits within the process space of the editor you are using.
The tray app is actually a launcher application that is required to support Query Analyzer since we are not able to simply register a plug-in with it as we are SQL Server Management Studio. The launcher application simply launches SQL Prompt 3 within the Query Analyzer process space when a QA instance is started up. It is not required for SQL Prompt 3 to run in SSMS and hence has no effect on whether or not it runs in SSMS. Exiting the launcher app also has no effect on running QA processes since SQL Prompt 3 will already be running in them.
The way way to completely disable SQL Prompt 3 is via the Options dialog, however you need to be aware that since SQL Prompt 3 will run in the process space of every running editor instance that it supports you need to (i) close all but one of your running editors, and (ii) disable SQL Prompt 3 via the Options dialog in the single remaining editor. You can then restart your other editors and SQL Prompt 3 will be disable.
HTH,
Bart
Add comment
Please sign in to leave a comment.
I right-clicked on the tray icon and chose "Exit", thinking that that would end the program.
After typing some more in Management Studio, I found out that the popups were still coming up. This also is the case with Query Analyzers that were open.
If I open a new Query Analyzer after exiting SQL Prompt, no prompts pop up. In new SSMS instances, they do.
Existing Query Analyzer instances do not gain the functionality after starting SQL Prompt, only new ones.