A link to this option should really be added to that annoying error dialog. I was having this dialog appearing on "everything" I tried to do in SSMS for any database on some of our servers (where I didn't have full rights).

If you were user-friendly, you'd have a checkbox saying "Don't show this message again for this server/database".

@TheSQLGuru installing the 6.1 beta will overwrite any existing install of prompt. If you need to get back to 5 for whatever reason you can always uninstall the beta and reinstall 5 from http://download.red-gate.com/checkforupdates/SQLPrompt/SQLPrompt_5.3.8.2.exe

I have 5.8.3.2 installed. Do I need to uninstall it before I install this build?

Please bring back the ability to stop SQL Prompt from loading certain databases - it is not just a matter of DB size, ever since switching to SQL 2012 and SQL Prompt 5.3, not be able to stop SQL prompt from loading objects for databases on remote machines has become a major performance issue.
Alter/notification message for SQL prompt needs to move away from screen edge so that it can be closed - you have to un-maximise the window in order to see the close button on the popup.

Concur with Richard's "include in" suggestion, especially when hosting a 3rd party DB that is never touched, or SSISDB for that matter.

Thanks @David, that worked.

I don't understand why this feature was removed. I work with a very large database and SQL Prompt 3.9.1 was fine - after upgrading to SQL 2012 and having to upgrade to SQL Prompt 5.3 this is now a big issue for me.

SELECT COUNT(*) FROM sys.objects
2052721

SELECT COUNT(*) FROM sys.tables
971826

SELECT COUNT(*) FROM sys.VIEWS
168636

The suggestion that Richard has come up with will also work for me.

Please ensure that SQL Prompt checks if it has enough memory, before it tries to import all columns in a database.

SupportWorks F0054593

Another customer seeking the return of this option. It was available in SQL Prompt V3.

"Hi Support,

SQL Prompt does not work on some of our databases.
We have several servers with production /test/development versions of a database with 70000+ tables.

It is ok that you cannot get SQL Prompt to work under these conditions, but we need a way to list database names that SQL Prompt must stay away from.
So that the entire SSMS does not crash as a result.

The current solution, where each and every pc must enter a list of server names and database names is not acceptable.
And our support contract is up for renewal on December 12th.

I’m looking forward to hearing your reply.

Best regards,
Henrik"

"Here is the main difference between 2 of our servers, one where SQL Prompt work, and one where it does not.
SELECT COUNT_BIG(*) FROM sys.objects

--12496 on t09
--70862 on vmp02

SELECT COUNT_BIG(*) FROM sys.columns
-- 194902 on t09
--4022975 on vmp02

Would it be possible for SQL Prompt to check if it has enough memory, before it tries to import all columns?
Or allow the uses to set a maximum of columns from each database?

Best regards,
Henrik"

This would be very helpful!

In my case the "opposit" property would be better:
list the names of databases, where the schemas are interesting/important for me.
Empty list: Prompt works on his "normal way"...