Network Management

After upgrading to SolarWinds Platform 2024.2, SCOM Monitor identifies the XTP configuration for SolarWinds database is not set according to the best practices

SCOM Monitor identifies that Solarwinds database is not using the best practices and shows the warning: "XTP configuration for database "SolarWindsOrion" on SQL Server instance "INSTANCE", computer "SQL-SERVER" is not set according to the best practices. Database with memory-optimized tables should be bound to a dedicated resource pool."

First published date

7/17/2024 1:29 PM

Last published date

6/4/2025 11:09 PM

Overview

Microsoft SCOM monitors the SQL instance for SolarWinds and is reporting a warning against the SolarWinds database since upgraded to the 2024.2 version.

Warning:

"XTP configuration for database "SolarWindsOrion" on SQL Server instance "INSTANCE", computer "SQL-SERVER" is not set according to the best practices. Database with memory-optimized tables should be bound to a dedicated resource pool."



Product section

Orion Platform

Cause

Memory-Optimized tables have been a standard part of MSSQL since SQL2016, and SolarWinds used this feature between 2018-2021. Still, it was disabled because some tables were becoming huge, resulting in database maintenance issues.

In the 2024.2 release, we enabled them again, but now only use db.entities and related tables (see below), which do not grow large and have no side effects like before.

Memory-Optimized tables

  • Cloud_Azure_LoadBalancerPoll_rel_1
  • Cloud_Azure_LoadBalancerStatus_poll_1
  • Cloud_Azure_SqlDatabasePoll_rel_1
  • ThresholdValue_history 

After the upgrade to 2024.2, SCOM detected the new version and threw a related warning.

All this info is also available in built-in SSMS reports if you right-click on the SolarWinds database in SQL Management Studio/Reports/Standard Reports/Memory Usage By Memory Optimized Objects (Note it will show only if there is data in the tables).

Resolution

This warning is expected / anticipated, especially following the developers' updates in version 2024.2, even though not all tables are set as memory-optimized.
The warning is by design, and unless performance issues arise, no immediate actions are necessary.

Binding a database to a resource pool is only available on the Enterprise version.

  • A database can be bound to only one resource pool. However, you can bind multiple databases to the same pool.
  • Before you can bind a database to a resource pool, both the database and the resource pool must exist.
  • The binding takes effect the next time the database is brought online.
  • You can bind a database to a named resource pool if, in the future, you want to create memory-optimized tables in the database.

The following Microsoft Article explains configuring memory-optimized tables to a resource pool.
Bind a Database with Memory-Optimized Tables to a Resource Pool

Additional Info
• Estimate Memory Requirements for Memory-Optimized Tables
• Bind a Database with Memory-Optimized Tables to a Resource Pool