up vote 2 down vote favorite
1
share [g+] share [fb]

We have a new installation of SQL Server 2005. The server doesn't have access to the internet and we've disabled the checks for certificate revocation but don't want to continue to do this as it is dangerous. But are still having these really slow start times (upwards of 60 seconds).

link|improve this question
75% accept rate
It would probably be helpful if you more accurately characterize what "really slow" means in your case? You should also probably mention if it's only slow on the first load or slow on every load. – Ryan Bolger May 20 '09 at 19:46
feedback

9 Answers

up vote 4 down vote accepted

In Tools - Options, go to the Environment - General section and for the At Startup option, select Open empty environment. See if that improves anything.

link|improve this answer
Worked like a charm! THANKS!!! Hopefully this will now be the conical answer instead of building firewall rules or proxy servers. – Keng May 21 '09 at 13:34
feedback
up vote 2 down vote

I hate using SSMS because it is slow and cumbersome. The older Enterprise Manager in SQL 2000 was quick to load and much snappier in reponse to actions. That's progress for you.

link|improve this answer
2  
+1 agreed; and find me something that loads as quick as query analyzer did. luckily it still works even with 2005/2008. I use sqlcmd more and more. Progress! – SqlACID May 21 '09 at 2:12
feedback
up vote 2 down vote

change your SQL Server Management Studio shortcut to have the nosplash switch at the end. This will prevent the SSMS Splash window from appearing on loading, which reduces loading time a bit.

the default would be:

"C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe" /nosplash
link|improve this answer
feedback
up vote 1 down vote

It's normally slow to open the first time after you start up your computer, but should get faster after that.

The reason is that it uses the .Net framework for some things, and that's probably the only .Net framework app you use on your machine. So the first time, all those assemblies (dlls) need to be loaded as well.

But this happens only once. From then on they're cached, and even if that cache is paged to disk the retrieval isn't too bad.

link|improve this answer
feedback
up vote 1 down vote

Have you applied a service pack to your instance and tools?

link|improve this answer
Yes, it's up to date. – Keng May 21 '09 at 13:31
feedback
up vote 1 down vote

This might work...

  1. Download the Certificate Revocation List from: http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl
  2. Create a path on a local web server for /pki/crl/products and put the CRL there.
  3. Create an entry on the hosts file (C:\Windows\System32\Drivers\etc) to put crl.microsoft.com to the IP address of that local web server.
link|improve this answer
What is this CRL used for? – Pure.Krome May 21 '09 at 1:54
It's the Certificate Revocation List that's checked to verify the certificate that signed the .NET code is still valid. More here: blogs.msdn.com/sqlserverfaq/archive/2009/05/05/… – K. Brian Kelley May 21 '09 at 2:01
feedback
up vote 0 down vote

Here's what we did. Since our proxy server is a white-list only, we set the connection in IE to use the proxy which then send a failure back immediately rather than waiting upwards of 60 seconds.

link|improve this answer
what are you talking about dude? When did SSMS use a proxy server? WTF? I've never heard of this... – Pure.Krome May 21 '09 at 1:53
2  
Proxy is set in IE. Therefore, by default, web based connections will go through that proxy. That includes by SSMS. – K. Brian Kelley May 21 '09 at 2:02
feedback
up vote 0 down vote

This won't be the final solution, but it sure helps: Edit the short cut for SQL Server Management Studio and add " /nosplash" to the end of the target field (without the quotes, of course).

That's assuming it is SSMS that is starting slowly. (edit: must be, just noticed the tag for it)

link|improve this answer
feedback
up vote 0 down vote

Another way to really speed up SSMS opening is right-click the shortcut for it, choose properties. Change the Target to this:

"C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe" -nosplash

The change is the addition of the -nosplash flag at the end. This will speed you up quite a bit opening. I learned this trick at SQL Saturday.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.