Server Health Indicator: Number of CPU Cores on SQL Server

Products

• Carbon Black App Control (formerly Cb Protection)

Issue/Introduction

System Health Indicator triggered with:

Number of CPU Cores on SQL Server
Too few CPU cores are available to SQL Server

Environment

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

Cause

The total number of Computers Supported exceeds the CPU Cores available to SQL Server.

Resolution

Health Indicator vs. OER

1. If on Server 8.11.0+ verify the Server Type is set correctly
   1. Log in to the Console and navigate to Settings > System Configuration General.
   2. Click Edit and change the Server Type accordingly (ex: VMware vSphere)
   3. Save the changes and refresh the Health Indicator in Settings > System Health.
2. Review the Operating Environment Requirements (OER): Tech Docs > Server Documentation > relevant version > Server OER.
3. Compare the Architecture by Endpoint Count against the Total Computers in the Console > Assets > Computers.

Steps when exceeding OER:

1. Verify Old Computer Cleanup is Enabled and configured correctly.
2. If using Template Computers or Template Images, verify Clone Cleanup Settings are configured correctly.
3. Review the Compute Capacity Limits for SQL Server.
   • Microsoft imposes a limits on total Sockets/Cores based on SQL Server Edition. If necessary, upgrade the SQL Server software.
   • If using a Virtual Machine for SQL Server it's possible a misconfiguration on Cores per Socket exists.
   • Assistance from your Database Administrator and/or Microsoft may be required to make changes.

Steps when at or below OER:

Open a case with Support and include:

• Database Performance Logs
• Full screenshot of the System Health Indicator that was triggered.

Additional Information

• In some instances the OER may change from version to version.
• An upgrade to App Control Server may be required to resolve, or could potentially trigger this Health Indicator.