23

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?

slhck
  • 235,242
Andrew J. Brehm
  • 5,342

16 Answers16

20

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.

Julien N
  • 568
18

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 crl.microsoft.com to 127.0.0.1

  • Exit SSMS
  • Press the keys [Win] + [R]

  • Enter the following..

    notepad %systemroot%\system32\drivers\etc\hosts.

  • Append the following..

    127.0.0.1    crl.microsoft.com

  • Save the file.

  • Start SSMS (ah! much better)
peco
  • 189
3

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: http://support.microsoft.com/kb/906892

Sk93
  • 153
3

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.

Brian Knoblauch
  • 4,911
3

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.

Vern Wold
  • 31
2

The solution for me was to disable the Hyper-V NIC:

enter image description here

Simply right-click and then click disable

Update 2021: Problem came back. This time it was a reverse DNS entry that solved it.

RobIII
  • 139
  • 1
  • 1
  • 9
2

For me, the problem was that my machine name was longer than is allowed by NETBIOS (15 characters). Once I shortened it, navigating SSMS became lightning fast.

Windows warns you if you try to set your machine name to longer than 15 characters -- I guess I should have heeded the warning!

Jeremy Prine
  • 21
2

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.

Neil Miller
  • 21
1

In my case it was not every time, but when it did, it would take 10 min to get back even my connection box. So I looked at Configuration manager and disabled shared memory. Works like charm every time !!

user61982
  • 11
1

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

1

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 127.0.0.1 (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).

Martin Marconcini
  • 1,539
1

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.

Drake
  • 5,734
0

I was having kind of same problem where Views folder was taking long time to expand. Other folders including databases or tables were OK. All of the recommendations above didn't work in my case. What worked for me is the user had sysdamin role, I removed the sysadmin role and give it back and everything start working fine for me.

Bader Cheema
  • 1
0

yups this worked for me. running from an elevated cmd prompt: reg DELETE “HKLM\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio” /reg:32

thao nguyen
  • 1
0
reg DELETE “HKLM\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio” /reg:32

Try this on admin cmd and agaiin try to install.

ZygD
  • 2,577
name
  • 1
-2

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

R Barbosa
  • 1