Activity overview
Latest activity by GearBahx
Hi,
I am also experiencing similar issues that I thought were originally my hardware. Now I have a brand new fresh i5 Windows 7 Ultimate x64 unit with 8 Gb or RAM. Lots of hard disk space, no garbage software. I am running SSMS 2008 R2 and SQL Prompt v5.1.6. Things start off well but during the course of the day as I open more query windows and attach to multiple servers/databases, SQL Prompt starts to get slower and slower and SSMS seems to get more sluggish. If I disable SQL Prompt, SSMS responds normally. If I quit SSMS and restart with SQL Prompt, the whole cycle starts again. I have also been seeing quite a few of these in the Application Event log:
2011-06-16 11:35:25,422 [14] ERROR RedGate.SqlPrompt.Engine.LogService [(null)] - LogService caught unhandled exception in AppDomain: 'Thread was being aborted.'
System.Threading.ThreadAbortException: Thread was being aborted.
at RedGate.SQLPrompt.CommonUI.TaskExecuter.Executer.ExecuteTask()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
or similar. All in all I have been really disappointed with this product since version 4. My old version 3 used to work awesome and there was more control of the app by the end user ( cache clean out, tweaking, etc ). But since then I think the quality has really dropped in this product badly. It's getting to the point where I may have to look for alternate products and not renew my maintenance when it comes due. I really like the product when it works, but when it doesn't, it really sucks !!! Please fix !
Max / comments
Hi,
I am also experiencing similar issues that I thought were originally my hardware. Now I have a brand new fresh i5 Windows 7 Ultimate x64 unit with 8 Gb or RAM. Lots of hard disk space, no garba...
Hi,
That could in effect work, but the problem is I am the DBA and have permissions to all objects ( and really need to keep it that way ). I guess I'll have to wait for the next version...
Max / comments
Hi,
That could in effect work, but the problem is I am the DBA and have permissions to all objects ( and really need to keep it that way ). I guess I'll have to wait for the next version...
Max
Filter candidate list based on DB owner
Hi,
I'd like to know if there is a way to "filter" the candidate list or the objects being caches so that, for example, only the objects belonging to "dbo" are shown. We have a large database that ...
Hi,
I would just like to report the same issues as everyone else. No VPN. 1 Gb NIC access to DB. No VPN. Everytime I drop a new SQL query into a new query window OR I open a new query window, the "Indexing Database object" semi-transparent box appear and takes forever to disappear , essentially making SQL Prompt virtually useless at this point and I am on the same DB!!!
What is going on here !!! / comments
Hi,
I would just like to report the same issues as everyone else. No VPN. 1 Gb NIC access to DB. No VPN. Everytime I drop a new SQL query into a new query window OR I open a new query window, the "...
I've always loved SQLPrompt 2 and had relatively few problems with it. We decided to go with SQLPrompt 3 because of the added features and to address some of the shortcomings of version 2. I like version 3 BUT it does tend to hang in SQL Server Management Studio's query window and in SQL Server 2000 Query Analyzer where version 2 never did. This version obviously needs more horsepower than version 2 because it is, for lack of a better word, sluggish. I've used both versions on a plain old P4 2 Ghz with 1 Gb of RAM. I have seen other posts in about sluggish performace and hangups and crashes. I hope these issues can be resolved in the next release. This really puts a rather big blemish on an otherwise fine and incredibly useful tool.
Max / comments
I've always loved SQLPrompt 2 and had relatively few problems with it. We decided to go with SQLPrompt 3 because of the added features and to address some of the shortcomings of version 2. I like v...