Note: This posting only applies to Management Studio 2005. We have corrected the behavior for Management Studio 2008 thus there is no special configuration necessary.
One of my co-workers recently responded to a problem a user was having with SQL Server Management Studio (SSMS). The user was experiencing extremely slow startup of SSMS – a couple of minutes. The potential cause for the problem is not apparently obvious, but could impact tons of installations.
One issue that can cause this problem is that if the server does not have access to the internet, then the .NET framework can't access the crl.microsoft.com website to verify that the digital signatures used to sign the binaries for managed applications are valid. Each certificate check has a 15 second timeout in the .NET runtime implementation. Depending on what features are installed, this can add up to a minute of startup time for Management Studio.
There are a couple workarounds:
1) Configure a proxy server to allow access to http://crl.microsoft.com from your server
2) Configure your firewall to return a failure status quickly when it blocks access to the http://crl.microsoft.com website
3) Disable checks for certificate revocation. You can do this using Internet Explorer by opening the Internet Options dialog, going to the Advanced Page, and then un-checking the "Check for publisher's certificate revocation" checkbox. There are fraudulently signed binaries in the wild that can make virus-infected applications look like they were published by Microsoft. Disabling this check should probably not be done on machines with internet access.
I think its shameful that so many applications, especially those written in .NET, run many times slower than apps released 5 years ago. Microsoft just has to keep soaking up that cpu to ensure the world keeps buys more pcs = more windows licenses. Sql Server 2000 finally became useable in 2005 when performance of servers and pcs got to circa P2500/1GB ram, and now they've made it unuseable once again.
Without applying this tweak sql 2005 takes 60 seconds to start on my laptop, and about 15 seconds with the tweak applied. It should start in < 1second.
Thanks, I had the same problem! I spend so much time looking for the answer!
It sets HKEY_USERS\[SID]\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell\Help\UseOnlineContent and HKEY_USERS\[SID]\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell\Help\UseOnlineContent\UseMSDNOnlineF1 to 0 from 1.
What do you think, can it be set in HKEY_USERS\.DEFAULT, too?
;) Google Is Your Friend :))
BTW MS KB article had been posted on August 8, 2006. :-)
PingBack from http://gubus2.wordpress.com/2007/04/10/sql-server-management-studio-lassu-indulas/
I've been for week with this annoyance. None of your tips worked, BUT when I was looking in the registry I found something...
This keys were pointing to a folder in machine that no longer is in my network !!!
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell
I changed both to a local directory, and now it's opening in less than five seconds !!!
Thanks for the hint !!!
THANK YOU! We spent days working with a frustratingly sluggish system only to discover that this was the source of our issues. In our case, it not only caused SQL MS to open slowly but it caused Identity Lifecycle Manager 2007 rules extensions to crash and timeout during sync runs (compiled in .NET 2.0 CLR).
Option #3 solved the problem!
Link back: http://idchaos.blogspot.com/2007/05/miis-sp2ilm-2007-timeouts-out-of-memory.html
This may not be the best place to ask this question, but we're really hug up. We have SQL2005 running on 64bit servers (w2003). Then we installed SQL2005 on a 32bit server (w2000), which installed, but with Management Studio!
Management Studio does not appear on the 32bit install CD's. Everything else lights up just fine.
Does anyone have any ideas/experience at finding the missing tool? (It's kinda slow working with the command line).
This issue is covered pretty well by blogs in the context of SSMS ( Dan Jones and Euan Garden ) and in
I am astounded that Microsoft insists on doing this. SQL is an enterprise product, and I don't know a single enterprise technician or security analyst that would allow a database server of any sort access to the internet, direct or otherwise. In fact, no server should be allowed access to the internet unless it is one of it's specific tasks. I would imagine that the hacking community are having a field day with the knowledge that Microsoft servers are operating like this.