Red Gate forums: SQL Prompt Previous Versions

RE: SQL Prompt - Unable to show database objects

AndrewJacksonZA — Wed, 03 Oct 2012 14:43:46 GMT

Code:

EXEC sp_ServerOption 'SERVER NAME', 'data access', 'true'

This worked for me, thanks Anu!

RE: SQL Management Studio 2005 hangs upon start

johnlwebb — Tue, 21 Aug 2012 16:29:45 GMT

I installed Red Gate SQL Developer Bundle and now both SQL Management Studio 2008 and Visual Studio 2008 get stuck on their splash screen when starting. has anyone found a solution to this?

RE: Does SQL Prompt 4 work with SSMS 2012?

peter.peart — Thu, 21 Jun 2012 12:51:44 GMT

Thanks for your post. SQL Prompt 4 isn't compatible with 2012 so you're not going to get it integrated within SSMS 2012.

You are going to need to upgrade your existing license, which the sales team will be more than happy to assist with. It will be cheaper for you than purchasing a new license outright.

If you want to upgrade, please just send an e-mail to sales@red-gate.com and we'll be happy to help.

Pete

Does SQL Prompt 4 work with SSMS 2012?

AndrewBA — Wed, 20 Jun 2012 04:36:26 GMT

Hi,

I have recently installed SQL Server 2012 on my machine, however the SQL Prompt 4 menu is not in the SSMS 2012 menu bar. I have uninstalled and re-installed SQL Prompt 4 but it still only appears in SSMS 2008.

SQL Prompt 5.3 does appear in both versions of SSMS but unfortunately I don't have a licence for this version!

Does anyone know how to get SQL Prompt 4 working with SSMS 2008?

Any suggestions will be gratefully received.

Cheers
Andrew

RE: AARGH!

thighfield — Mon, 19 Mar 2012 16:40:17 GMT

I had the same thing happen, but through a little trial and error, I figured out what the combination of keystrokes was...for me at least. I had typed "CASE" followed by a space, which brought up the intellisense dropdown. Next, I pressed Ctrl-DownArrow, which switched the intellisense window to "snippets" mode. Next, I pressed UpArrow, which selected the bottom item in the list, which just happens to be "yell". Lastly, I pressed Enter.

RE: AARGH!

stealth210 — Wed, 08 Feb 2012 22:40:03 GMT

terry-s wrote:

From the query editor window, click ctl-space to bring up the SQL prompt window, type "yell" and hit enter.

Yes, I see that does it also. However, my key combination and most likely the combination of the original poster was not y-e-l-l anything. The 2 times it has happened to me, I was no where near those letters.

RE: AARGH!

terry-s — Wed, 08 Feb 2012 22:35:47 GMT

From the query editor window, click ctl-space to bring up the SQL prompt window, type "yell" and hit enter.

RE: AARGH!

stealth210 — Fri, 27 Jan 2012 16:30:23 GMT

I know this is an ancient thread, but I just ran into this as well. It's not a problem, but I have no idea how I did it. I think it was a sequence of some of the following in some order: ctrl, shift, up, esc in quick motion (mis key). It definitely was not 'yell' tab.

It's funny when it comes up (2nd time ever), but I have no idea how I did it. SQL Prompt Pro 5.2.0.5.

RE: cache permission issue with 3.9 and 2008 r2

Anu Deshpande — Tue, 20 Dec 2011 13:49:20 GMT

Many thanks for our post and apologies for the inconvenience caused.

I can suggest you two things:

1. Make sure you are on latest SQL prompt 3 version: ftp://support.red-gate.com/patches/SQL_Prompt/SQL_Prompt_3.9.3.303.zip

2. And also for SQL 2008 servers it may be necessary to grant VIEW SERVER STATE explicitly to access information about encryption keys otherwise a 'User does not have permission to perform this action' message may prevent the display of candidates.

Kindly let me know if any of the above solves the issue you are having.

cache permission issue with 3.9 and 2008 r2

merk — Mon, 19 Dec 2011 12:48:19 GMT

I've tried specifying the SA login for this database, to no effect. I also tried specifying a false login for this database and i get the same results. So i'm wondering if sql prompt is actually using the login i provide or not.

The SA login should have sufficient permissions to cache this database, so i have no idea why it's failing.

As a test i installed the latest version of sql prompt, and it has no problem caching the database. So it seems like it might be a bug in 3.92 ?

Here's the full error message:

Unable to refresh or cache database [5.114.xxx.yyy].[xyz] due to the following error: The user does not have permission to perform this action..

RedGate.SqlPrompt.Engine.Cache.DatabaseRefreshException: Unable to refresh or cache database [5.114.xxx.yyy].[xyz] due to the following error: The user does not have permission to perform this action.. ---> System.Data.SqlClient.SqlException: The user does not have permission to perform this action.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at v.a(String )
at v.ExecuteSqlSetting()
at o.aa()
at o.a(n )
at RedGate.SQLCompare.Engine.Database.RegisterForSqlPrompt(ConnectionProperties connectionProperties, Options options, Boolean includeSystemObjects, Boolean includeDependencies)
at cy.b(IAuthenticationTokenProvider )
--- End of inner exception stack trace ---
at cy.b(IAuthenticationTokenProvider )
at cy.a(IAuthenticationTokenProvider )
at cy.GetMetaData(IAuthenticationTokenProvider provider)
at M.b(G , IAuthenticationTokenProvider , Boolean , EventHandler`1 , EventHandler`1 , EventHandler`1 , EventHandler`1 )

RE: Unable to refresh or cache database

Trevorwin — Thu, 27 Oct 2011 14:17:13 GMT

Couple of things to check...

Try using IE to open the following URL...http://testserver01/Store/SiteCacheRefresh.axd?CacheToRefresh=AllMarketingCaches'.

Is the IIS web site where the Commerce site is configured set to use host headers? If so, try adding the machine name as a host header for the site and see if IE will then work on the URL.

Also, check that the app pool that the web site is running under is set to use the correct identity.

RE: SQL Prompt v3.6 & SSMS 2008 R2

james.billings — Thu, 25 Aug 2011 19:59:28 GMT

When you originally purchased the product, you could have taken out support and upgrades with it (this is often for 1 year, 3 years etc).

If this is purchased, then your support queries are handled at a higher priority, and you are entitled to upgrades for free until your support contract expires.

RE: SQL Prompt v3.6 & SSMS 2008 R2

downatone — Thu, 25 Aug 2011 19:57:40 GMT

Thanks for the response James.

Whats a support&upgrades bolt-on?

RE: SQL Prompt v3.6 & SSMS 2008 R2

james.billings — Thu, 25 Aug 2011 19:45:04 GMT

A serial will always allow you to use any point release - so if you're using 3.6 you'd be fine with 3.9 for instance. It's only relevant when it comes to major releases (i.e. 3.x > 4.x) whereupon you'd then need a support&upgrades bolt-on for the serial number to get a free upgrade.

RE: SQL Prompt v3.6 & SSMS 2008 R2

downatone — Wed, 24 Aug 2011 13:00:00 GMT

Thanks Brian - that did the trick - didn't realize my serial # would be valid for version higher than 3.6.