Environment
NetIQ AppManager 6.x
NetIQ AppManager 7.0.x
Microsoft SQL Server 2000 Advanced
Microsoft SQL Server 2005 Enterprise
Situation
What are the recommended Microsoft SQL Server memory settings for the AppManager Repository (database)?
AppManager Operator Console may be unresponsive
Timeout Expired messages written to rplib.log on AppManager Operator Console
Microsoft SQL Server Process (sqlservr.exe) Consuming More Than 80% Memory Usage when Checked within Windows Task Manager
AppManager Operator Console may be unresponsive
Timeout Expired messages written to rplib.log on AppManager Operator Console
Microsoft SQL Server Process (sqlservr.exe) Consuming More Than 80% Memory Usage when Checked within Windows Task Manager
Resolution
The recommended setting for the AppManager Repository (QDB) database is 'fixed memory size' set to equal about one quarter of the total physical memory allocated to the Microsoft SQL Server.
To check the memory settings on Microsoft SQL Server:
- Open SQL Server Enterprise Manager or SQL Management Studio.
- Expand the SQL Server Group.
- Select the appropriate SQL Server.
- Right-click on the SQL Server.
- Select Properties.
- Click on the Memory tab. This will display the memory configuration settings (dynamic or fixed) for the Microsoft SQL Server.
NOTE: If any changes are made to these settings, SQL Server must be stopped and restarted This can be done within SQL Server Enterprise Manager by right-clicking on the SQL Server and selecting Stop (and Start).
Additional Information
Formerly known as NETIQKB24961
When setting the memory to dynamically adjust, Microsoft SQL Server 2000 and 2005 dynamically allocate and de-allocate memory within the buffer cache to optimize performance. They base the amount of memory used on the Microsoft SQL Server's load, and competing memory requirements from other server applications. If all available physical memory is already committed to a server application, it takes processor cycles to reallocate memory between server applications. When memory is almost completely consumed it will degrade the performance of your AppManager Repository database.
When setting the memory to dynamically adjust, Microsoft SQL Server 2000 and 2005 dynamically allocate and de-allocate memory within the buffer cache to optimize performance. They base the amount of memory used on the Microsoft SQL Server's load, and competing memory requirements from other server applications. If all available physical memory is already committed to a server application, it takes processor cycles to reallocate memory between server applications. When memory is almost completely consumed it will degrade the performance of your AppManager Repository database.