IMPORTANT ANNOUNCEMENT: On May 6, 2024, Carbon Black User eXchange (UeX) and Case Management will move to a new platform!
The Community will be in read-only mode starting April 19th, 7:00 AM PDT. Check out the blog post!
You will still be able to use the case portal to create and interact with your support cases until the transition, view more information here!

App Control: RAM for SQL Server Has Gone to Severity Red

App Control: RAM for SQL Server Has Gone to Severity Red

Environment

  • App Control Server: All Supported Versions
  • Microsoft SQL Server: All Supported Versions

Symptoms

A Health Indicator in the Console states:
'Health Indicator 'RAM for SQL Server' has gone to severity red. Check the Health Indicator for more details.'

 

Cause

The memory limit for SQL Server is not set correctly for the total number of endpoints.

Resolution

Set the memory limit for SQL Server according to the requirements specified in the SQL Server Configuration guide: VMware Docs > Server Documentation > SQL Server Configuration Guide > SQL Permissions & Memory Configuration.
  1. Open SQL Server Management Studio and connect to the SQL Server hosting the das database.
  2. In the left-hand pane > Object Explorer > right click Server Name > Properties > Memory.
  3. Verify the value, 'Maximum server memory (in MB)' is set according to the OER.
  4. Restart SQL Server (right click the Server Name > Restart).
  5. Restart the App Control Server and Reporter services.

Additional Notes

  • By default SQL Server is configured to use the full system memory.
  • The Memory Limit required for App Control is dependent on the total Computers in App Control.
  • The SQL Server Memory Configuration can be found in VMware Docs > Server Documentation > SQL Server Configuration Guide > SQL Permissions & Memory Configuration.
  • SQL Express has a built-in memory cap of 1GB.

Related Content


Labels (1)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎11-03-2022
Views:
615
Contributors