Microsoft SQL Server Management Studio 2005 is to 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

  1. Exit SSMS
  2. Press the keys [Win] + [R]
  3. Enter the following..
    notepad %systemroot%\system32\drivers\etc\hosts.
  4. Append the following..
  5. Save the file.
  6. Start SSMS (ah! much better)

The reason why it is slow is because .Net Runtime tries to contact to ensure that the certificate in various .Net packages that were shipped with SSMS is valid.
If you are behind a firewall/proxy as is the usual case then there is no direct route out to the internet to to validate the certificate(s) and it eventually times out. The wait for the time out causes the delay for each and every package it checks.

With the change to the HOSTS. file, you are forcing the certificate checks to to route to the local host which immediately fails and the certificate checks are ignored.

SQL Server Management Studio may also be configured to use online help recourses, while the host computer may not have access to the online resources.

First Step:

  1. Go to “Start” -> “Programs” -> “Microsoft SQL Server 2005”.
  2. Open “SQL Server Management Studio”.
  3. Navigate to “Tools”  -> “Options” -> “Help” -> “Online”.
  4. Mark the checkbox “Try local first, not online”
  5. Press on “Ok” button.
  6. Restart SQL Server Management Studio”.

Tip: In some cases you may need to disable “Check for publishers certificate revocation” option under the Internet Explorer -> “Internet Options” -> Advanced”.

Second Step:

  1. Go to “Start” -> “Programs” -> “Microsoft SQL Server 2005”.
  2. Open “SQL Server Error and Usage Reporting”
  3. Uncheck the following checkboxes:
    a.”Send error reports for all components and instances of SQL 2005 to Microsoft or your corporate error reporting server.”
    Note: Using local “corporate error reporting server”, may require to enable this feather.
    b. “Send feather usage reports for all components and instances of SQL 2005 to Microsoft.”
  4. 4. Press on “Ok” button.
Posted in Microsoft, SQL and tagged , , , .

Leave a Reply