SQL Server Management Studio slow startup times
JP7
Posts: 17
Hi
Since installing SQL Prompt 5.0.1.7 I've been experiencing extremely slow startup times of SSMS 2008 R2 and VS2010.
I noticed that two entries get recorded in the logs:
07 Mar 2011 06:48:55,313 [10] ERROR RedGate.SqlPrompt.Engine.LogService - LogService caught unhandled exception in AppDomain: 'Thread was being aborted.'
System.Threading.ThreadAbortException: Thread was being aborted.
at RedGate.SQLPrompt.CommonUI.TaskExecuter.Executer.
Since installing SQL Prompt 5.0.1.7 I've been experiencing extremely slow startup times of SSMS 2008 R2 and VS2010.
I noticed that two entries get recorded in the logs:
07 Mar 2011 06:48:55,313 [10] ERROR RedGate.SqlPrompt.Engine.LogService - LogService caught unhandled exception in AppDomain: 'Thread was being aborted.'
System.Threading.ThreadAbortException: Thread was being aborted.
at RedGate.SQLPrompt.CommonUI.TaskExecuter.Executer.
Comments
Slow startup times can be caused by the Check for Updates mechanism not managing to reach our server. Please try going to the SQL Prompt 5 menu and choosing Check for Updates... Then uncheck the box in the bottom-left corner called Check for updates on startup.
Please post here whether this has helped or not.
We are tweaking the Check for Updates mechanism in SQL Prompt 5.1 so that even if your machine can't reach our server easily, it still doesn't slow down the startup of SSMS.
Cheers,
Paul
Project Manager, Red Gate
Your suggestion dramatically improved the load times. Looking forward to V5.1.
Cheers,
Jean-Paul
and it says I have the latest version 5.1.8.2, and I unchecked
"Check for updates on startup"
but it still takes 30 seconds to start up SSMS.
One must use a proxy on our network to get outside, so that may interfere with phoning home.