Microsoft KB Archive/945068

= Some visual elements in SQL Server Management Studio lose functionality when you register many instances of SQL Server =

Article ID: 945068

Article Last Modified on 12/12/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Workgroup Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows XP and Windows Vista



SYMPTOMS
When you register many instances of Microsoft SQL Server in SQL Server Management Studio, some visual elements in SQL Server Management Studio lose functionality.

For example, you encounter the following issues in SQL Server Management Studio:
 * Some menus are unavailable.
 * Some menus do not display completely.
 * Some server activities cannot finish.
 * The copy operation and the paste operation cannot succeed.

This behavior is likely to occur when more than 200 instances of SQL Server are registered in SQL Server Management Studio.

Additionally, you are likely to experience issues that are related to the desktop heap when a process involves replication. For example, issues that are related to the desktop heap occur when a publisher and more than 200 distribution agents push data to 200 different subscribers.



CAUSE
When you register an instance of SQL Server in SQL Server Management Studio, SQL Server Management Studio consumes memory from the desktop heap. Depending on the visual element that the registration uses and on the size of desktop heap, the desktop heap may be used up. When this occurs, you encounter the issues that are described in the &quot;Symptoms&quot; section.



WORKAROUND
To work around this behavior, use one of the following methods.

Method 1
Reduce the number of instances of SQL Server that are registered in SQL Server Management Studio.

Method 2
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Increase the size of the desktop heap for the interactive window station at which SQL Server Management Studio is running. To do this, follow these steps:  Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey:

 Double-click the Windows registry entry. In Value data section of the Edit String dialog box, locate the SharedSection entry. Increase the second value of the SharedSection entry.

Notes
 * The second value of the SharedSection entry represents the size of the desktop heap for each desktop that is created in the WinSta0 interactive window station. The size is in kilobytes (KB).
 * By default, the second value of the SharedSection entry is 3072 in Windows Server 2003.

<div class="status_section">

STATUS
This behavior is by design.

<div class="moreinformation_section">

MORE INFORMATION
You can use the Desktop Heap Monitor tool to verify that the issues that you encounter are caused by the limited size of the desktop heap.

The following file is available for download from the Microsoft Download Center:

Download the DesktopHeapMonitor8_1_2925_0.exe package now.

<div class="references_section">