Governing Memory for Database Child Processes

Starting in Strategy (September 2026), the database child-process memory governor limits creating new database connections when the combined memory usage of existing database processes reaches a configured percentage of the server's total physical memory.

If the governor triggers and the limit is exceeded, the following error message displays: Failed to create new DB connection. The memory used by DB connection child processes has exceeded the maximum limit. Please contact the system administrator for assistance.

Governing Setting

The following setting is introduced to control the governor:

DssServerMaxDbChildProcessesMemoryPercent

The limit is calculated using the following equation:

total physical memory * setting percentage / 100

The governor collects unique database worker-process IDs from existing connection monitors and compares their total memory usage with this limit.

Connections to the metadata-server and distribution-service are allowlisted and not blocked by the governor to ensure platform resilience.

Define the Setting

1. Open the Strategy REST API Explorer by appending /MicroStrategyLibrary with /api-docs/index.html?visibility=all in your browser.

2. Create a session and authenticate it. In the Authentication section, use POST /api/auth/admin/login.

3. Click Try Out and modify the request body by providing your username and password.

4. Click Execute.

5. In the response, find X-MSTR-AuthToken.

6. Under the System Administration section, look up PUT /api/iserver/settings.

7. Click Try Out.

8. Set the proper X-MSTR-AuthToken from step 5.

9. Set request body as follows:

   Copy

   {
     "settings": [
       {
         "id": 205,
         "dataType": 3,
         "value": "80"
       }
     ]
   }

10. Click Execute.

11. The setting takes effect immediately. No server restart is required.

To confirm the change, repeat the steps above but replace the code in step 6 with GET /api/iserver/settings and view the response value.