Service Manager Database RAM: Reducing High Memory Usage

An unusually large or steadily-growing memory footprint on a System Center Service Manager database server is often traced back to SQL Server Analysis Services (SSAS), which backs the Service Manager data warehouse, rather than the SQL Server relational engine itself.

What Fixed It

Rather than the commonly-suggested approach of simply raising SQL Server’s max memory limit higher and higher, setting an explicit memory ceiling within the Analysis Server properties — specifically the memory settings that control how much SSAS is allowed to consume for processing and caching — brought usage under control and kept it stable.

Result

After applying a defined SSAS memory limit, RAM usage stopped climbing to the configured ceiling, and it was possible to actually lower the memory allocated to the VM afterward without performance regressing. This was stable over several weeks of monitoring following the change. If you’re chasing a similar issue, check the Analysis Services instance’s memory properties (in SQL Server Management Studio, under the SSAS instance’s Properties > General/Memory settings) before assuming it’s purely a SQL Server relational engine tuning problem.

Service Manager Is Still Around — And Still Uses This Same Architecture (Updated for 2026)

Worth confirming up front, since a lot of System Center components have quietly been retired over the years: System Center Service Manager has not been dropped. It’s part of the current System Center 2025 wave, with a fixed lifecycle running mainstream support through 8 January 2030 and extended support through 9 January 2035 — so if you’re still running it, it remains a fully supported product, not a legacy holdover you need to plan an exit from. The underlying architecture this fix targets hasn’t changed either: the data warehouse is still SSAS-backed, so the same “set an explicit SSAS memory ceiling rather than just raising the SQL Server limit” approach remains the right first place to look if you’re seeing the same symptom on a current SCSM 2022 or 2025 deployment.

Resources

• virtual machine