Dan's Blog

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.

http://support.microsoft.com/kb/555686.

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?

Erik: http://www.google.hu/search?hl=hu&q=sql+management+studio+starts+slow&meta=

;) Google Is Your Friend :))

BTW MS KB article had been posted on August 8, 2006. :-)

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

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 !!!

Link back: http://idchaos.blogspot.com/2007/05/miis-sp2ilm-2007-timeouts-out-of-memory.html

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.

Thanks for issue. Resolved in my case.

PingBack from http://alonzo.mediaplusnews.info/sqlservermanagementstudio.html

We've got a Microsoft Enterprise CA system.  Is there a way to leverage the certs which could be issued from it as well as our CRL?  It would be much less of a threat than opening a hole to the Internet.

We have a client that experiences this certificate verification problem using a 3rd party application (not SQL Server Management Studio) and will try the hosts change.

But, we have the same software installed on our test servers and on the developer's servers and don't experience this attempt to get out to the internet. We have sniffers and have checked.

So, why does one system do this verification and others not? There must be a setting that is causing this verification to occur. We have checked the internet explorer settings and they are the same. We have checked other local policy settings relating to certificates and they are the same.

I'd prefer to find out why it is verifiying rather than just diverting the check or implementing a workaround.

Any ideas?

Thanks.

Thanks Dan.

We are in contact with the vendor however they also do not know.

We have tested a few workarounds (including the hosts change) and the only one that works is to change Internet Explorer security settings to NOT "check for publisher's certificate revocation".

Still don't know why it is checking for publisher's certificate revocation when other installations of the same software do not.

The problem occurs when the app is run from a client PC/laptop or from the server.

Could their server have some bad certificates loaded?

Any other ideas?

Thanks,

Mark.

AHA!

I was dealing with FIM2010 RC0 with the Password Reset workflow (just getting setup) and was down to everything working EXCEPT after password reset wouldn't go through.  Checked logs on ILM and found an MMS fail when I tried.  Took a shot and did option #3.  Now of course I'm running about a billion updates to the Server 2008 Enterprise ILM server.  Either we're blocked or my certs are out of date.  Hopefully the updates fix this :)

THANKS OH MIGHTY ILM MVP'S.  YOU MADE THE DAY!