Tuning memory in SQL Server
Tuning memory in SQL Server
|
| Release 9.3 |
   |
Note:This topic was updated for 9.3.1.
NOTE: Applies to geodatabases created with an ArcGIS Server Enterprise license only
By default, SQL Server will use as much memory as it requires. On busy systems, SQL Server can force other applications, including ArcSDE, to page, compromising their response time and scalability. Consider limiting SQL Server's memory consumption by using a fixed memory size or setting a maximum memory size. To do this in SQL Server 2000, right-click the server in the Enterprise Manager and click Properties. On the Properties page, click the Memory tab and hard code a memory limit or set an upper boundary to 50 percent of total RAM. Adjust up or down as necessary. For SQL Server 2005 and 2008, right-click the server in Management Studio and click Properties. Click the Memory page and type an amount for the Maximum server memory.
You can also boost SharedSection in the registry. This setting controls the heap size for noninteractive desktop applications—the amount of memory available to spawn and support Windows services such as ArcSDE client connections. Adjust this setting if you anticipate having more than 50 concurrent ArcSDE connections. Locate this setting in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems under the Windows entry. This entry contains a string, contained in which is SharedSection=1024,3072,512. Increase the last entry to 1024.
