How disable SQL Prompt 5 in Visual Studio 2012?

Ah yes, that suggestion was created a couple of days after my last comment. Thanks for putting a link to it here!

I found one here: http://redgate.uservoice.com/forums/94413-sql-prompt-feature-suggestions/suggestions/3377469-eliminate-or-reduce-the-need-to-continuously-conn

Adam: You're right -- I can see that getting frustrating very quickly if you do a lot of SQL editing in Visual Studio. I searched the UserVoice forum for references to this and couldn't find anything already posted though. Could you add a request so that it's more visible? Then others can add their vote if it's important to them too.

So if I'm working with 3 stored procedures and 3 user defined functions in my VS database project I have to log in 6 times?! And if I close the document and reopen it I have to log in again? Wow. No wonder I thought the connection was dropping. That's makes it almost unusable. It'd be better if the connection was per VS instance. If I had to work with multiple databases I'd just open another instance of VS.

Hi Adam: SQL Prompt in Visual Studio currently requires you to connect to the server manually using "SQL Prompt 5 > Connect to Server...", and you have to do this for each new query window. Is this what you're seeing, or are the connections being dropped even with a single query window open after you've connected?

This works well now, although it seems to disconnect often in VS 2012. Is there some condition that would cause the connection to my local database to drop, forcing me to reconnect often to get intellisense, or is this a bug?

Any updates on when this patch will be released for VS2012 (SQL Prompt)?

Cory - Thanks for the feedback, we just need to do the final testing of our Visual Studio (VS) 2012 support in SQL Prompt, so, it is coming, and you should see an update available shortly!

Ed - I don’t believe there should be a problem using SQL Prompt in SQL Server Management Studio (SSMS) 2012 without VS 2010 SP1 installed. SSMS 2012 operates in an isolated shell, quite independent of your main VS install, and uses a distinct SQL Prompt addin dll.

SQL Server Data Tools (SSDT), an extension package for VS 2010 included as part of the SQL Server 2012 install, does require that you’ve upgraded VS 2010 to service pack 1. The installer will warn you if VS 2010 < SP1 is found. Perhaps this is the requirement you’re seeing when installing SQL Server 2012? If this isn’t the case – could I ask you to contact our technical support (support@red-gate.com) with specific details? Thanks!

If you have both SQL Server 2012 and Visual Studio 2012 installed, I don't see how you can use SQL Prompt (unless you also have Visual Studio 2010 SP1 simultaneously installed). Apparently, SQL Server Management Studio (SSMS) in SQL Server will not work without VS 2010 SP1 installed, so if you uninstall that to install VS 2012, you cannot use SSMS. Since SQL Prompt does not currently work with VS 2012, then I don't see how you can use SQL Prompt at all with just the 2012 versions of both programs installed.