Observability

Performance Degradation and Database Size Limitations in SolarWinds Platform When Using SQL Express in Production Environments

This article provides information about the limitations and unsupported use of Microsoft SQL Server Express (SQL Express) in production environments for the SolarWinds Platform, including potential performance issues, database constraints, and recommendations for resolution.

First published date

8/21/2025 2:28 AM

Last published date

8/21/2025 2:28 AM

Overview

In SolarWinds Platform deployments, the database server plays a critical role in maintaining performance and scalability. For production environments, the SolarWinds Platform server and the SolarWinds Platform database must be hosted on separate servers, which can be physical or virtual machines. If the SQL Server is deployed on a virtual machine, the database must be maintained on a separate physical drive to ensure optimal performance and avoid resource contention.

 

Starting with SolarWinds Platform version 2022.3, Express editions of supported Microsoft SQL Server versions (such as SQL Server 2016 SP1/SP2/SP3, 2017, 2019, or 2022 CU1 or later) are not supported for production use. They are only recommended for evaluation purposes. SQL Express can be installed on the same server as the SolarWinds Platform server for evaluations, but it introduces significant constraints that make it unsuitable for production.

 

Key limitations of SQL Express include:

 

  • Maximum database size of 10 GB.
  • Computing capacity limited to the lesser of 1 socket or 4 cores for the SQL Server Database Engine, Analysis Services, or Reporting Services.
  • Maximum memory for buffer pool per instance: 1410 MB.
  • Maximum memory for Columnstore segment cache per instance: 352 MB.
  • Maximum memory-optimized data size per database: 352 MB.
  • Support for up to 100 SolarWinds Platform groups.
  • Up to 5 concurrent users logged in simultaneously.
  • Performance can be negatively impacted by complex groups, limitations, or alerts.

 

In a production setup, even a minimal SolarWinds Platform installation (including deployments like Core Platform, NTA, and Log Analyzer) can quickly approach or exceed these limits. For example, the combined database size for an empty system may start near 8 GB, leaving only about 2 GB for additional data, which could be consumed within hours of monitoring activity. Customers may observe symptoms such as:

 

  • Slow query response times or overall system lag.
  • Alerts or errors related to database capacity, such as messages indicating "Database full" or "Exceeded maximum size."
  • In logs (e.g., application or SQL Server logs), entries might resemble: "The database 'SolarWindsOrion' has reached its size quota" or performance warnings like "Resource governor reconfiguration".

 

These issues are more pronounced in multi-module deployments or environments monitoring more than a few hundred elements, where latency between the SolarWinds Platform engine and database should remain below 200 ms (with potential degradation above 100 ms).

Product section

Hybrid Cloud Observability

Cause

The issue arises from using SQL Express in production environments, which violates SolarWinds Platform system requirements. SQL Express is designed for lightweight, evaluation scenarios and cannot handle the data volume, query complexity, or scalability demands of a production SolarWinds deployment. Factors contributing to this include:

 

  • Rapid growth of database size due to monitoring data, logs, and module integrations exceeding the 10 GB limit.
  • Insufficient CPU, memory, and I/O resources leading to bottlenecks.
  • Historical changes in support policy: Prior to version 2022.3, SQL Express was unofficially allowed for very small setups, but it is now explicitly unsupported for production to ensure reliability.

 

This can be exacerbated in small or low-end customer environments where resource constraints are tighter, but the core cause is the mismatch between SQL Express capabilities and production needs.

Resolution

To resolve this issue in production environments:

  1. Migrate to a supported SQL Server edition (Standard or Enterprise) on a separate server from the SolarWinds Platform server. Ensure the database is on a dedicated physical drive if using a virtual machine.
  2. Review your deployment size and align with SolarWinds Platform guidelines:
    • For small evaluations only: Use SQL Express temporarily, but monitor database size and performance closely.
    • For production: Provision hardware meeting minimum specs (e.g., dual quad-core CPU, 16 GB RAM for medium environments).
  3. Perform database maintenance: Switch to Simple recovery mode for better performance (or Full if using clustering/Always On), and schedule regular backups.
  4. If your environment is very small and cost is a barrier to adopting full SQL Server (e.g., additional VM setup), this is currently a product limitation. Submit a feature request through SolarWinds support to evaluate reconsidering SQL Express supportability for low-end customers, including guidance on scale thresholds, retention recommendations, and known limitations.