Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Considering that Microsoft SQL Server is not, technically, a slow database management system, I keep wondering why it often/usually takes such a long time for SQL Management Studio to connect.

This happens even when nobody else is accessing the database server and when Management Studio runs on the same machine as SQL Server.

Plus SQL Management Studio often takes a very long time to do something, even just displaying a login's permissions can take several minutes on database servers otherwise unused.

Is there some obvious explanation?

share|improve this question
How long is "so long"? 2 seconds, 20 seconds or 200 seconds? – Bevan Jul 24 '09 at 1:15
Do you have any odd plugins? Every server I try to connect to takes under 2 seconds on my work network. – Bob King Aug 4 '09 at 20:38
@Bevan for me, minutes to connect to localhost... it's truly frustrating. (YMMV) And it started at some recent point in time, it was never like this before. – ANeves Nov 6 '12 at 19:13

10 Answers 10

up vote 5 down vote accepted

This sounds stupid but I had a problem of a very slow SQL Server Management Studio and this trick solved it:

  • Open Internet Explorer
  • Go to Tools -> Internet option
  • Open the "Advanced" tab
  • Uncheck "Check for server certificate revocation (requires restart)"

This trick is only effective if the computer where your SQL Server Management Studio is installed is NOT connected to Internet. Only doing that solved my problem. Maybe it will solve yours.

share|improve this answer
Oddly enough this seems to improve things a bit. But the 32/64 bit issue mentioned below could also be right. I'll accept this answer and upvote the other. – Andrew J. Brehm Aug 25 '09 at 14:22
I'm not a security expert, but this page (which is represented in another answer here and worked well for me) notes that disabling security cert checking is not advised. I would think that taking this approach opens you up to a nice big security risk :O – jinglesthula Jan 31 '14 at 16:52
In my case, the server wasn't connected to the Internet so it couldn't perform any security check, so it didn't change much, except after that I didn't have to wait for the timeout :). But I agree this is not a good idea on a server that can perform this check. – Julien N Feb 3 '14 at 17:29

This worked for me: Microsoft SQL Server Management Studio is too Slow

In a corporate environment it is not uncommon for Microsoft SQL Server Management Studio (SSMS) for SQL Server 2005 to take over 45 seconds to start as well as lags and delays when opening various windows and dialog boxes from within the application. If you are experiencing this issue, then a quick fix is to add an entry in your HOSTS. file that points to

  • Exit SSMS
  • Press the keys [Win] + [R]
  • Enter the following..

    notepad %systemroot%\system32\drivers\etc\hosts.
  • Append the following..
  • Save the file.

  • Start SSMS (ah! much better)
share|improve this answer
My god, it's bizzare... – Alex Zhukovskiy Jul 4 at 15:44

by default, when connecting to a local server, the network protocol used is shared memory. This can be quite slow sometimes.

I was experiencing the same speed issue when connecting to a similiarly specced box locally, but not remotely.

Do you get the same slowdown if you specify the TCP/IP network protocol when connecting?

EDIT Also, according to Microsoft, this may be an issue caused by Management Studio being 32bit and being run on a 64bit OS. See here:

share|improve this answer

Possible broken IPv6 implementation? Are you running dual-stack? We are and have had this problem before. IPv6 is tried first, and if there's any configuration errors it'll eventually fail to IPv4.

share|improve this answer

SSMS is attempting to check with Microsoft for the default root certificate, even though it does not us it. If you are using a proxy server use either proxycfg or netsh to set the system proxy settings. Close and then open SSMS and the time to load will be greatly reduced.

share|improve this answer

My colleague has the exact behavior as you on his PC. He was using SQL Server Management Studio of 2005. He solved installing the new version that comes with SQL Server 2008.

If you notice that this problem happen only on your PC I suggest you to try uninstall and re-install the whole Microsoft SQL Server suite.

share|improve this answer
This happens to me with both SQL Server 2005 and 2008. – Andrew J. Brehm Jul 20 '09 at 13:21

Could this be a Name Resolution problem? If the SQL Server engine is on the same machine, try using (local) as the name or even (or the IP address of the machine). Netbios over TCP/IP and/or deficient WINS/DNS can lead to slow connecting times.

Also make sure that the server has enough memory to operate. SQL Server can work well under 512 MB ram, but the performance degrades very fast.

There shouldn't be a delay longer than 5 secs when connecting to a server. (Less if local).

share|improve this answer
No. It connects to ".". The servers in question are 64 bit and have 8 GB and more. – Andrew J. Brehm Jul 27 '09 at 8:43

I added sqlservr.exe to the exception list of the windows firewall on SQL server 2005. Result: very quick respons!

share|improve this answer

Adding to Julien N 's answer above, I fixed the problem (a 10-second delay when running a query the first time) by un-ticking:

"Check for Publisher's certificate revocation"

in Internet Explorer advanced options. No restart required.

share|improve this answer

If you're using SQL Express, check that the total size of your databases does not exceed 10 GB (limitation for SQL Express 2012).

share|improve this answer
If the size exceeds the limitation, would the result be just slow performance? – fixer1234 Nov 12 '15 at 17:10

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .