SCSM Database Migration: Moving to a New SQL Server

Migrating a System Center Service Manager (SCSM) database — moving the Service Manager and Data Warehouse databases to new SQL Server hardware — is a supported but involved process, and it’s worth treating as a planned maintenance project rather than a quick task.

High-Level Process

1. Stop the System Center Data Access and Config services on all Service Manager management servers.
2. Back up all relevant databases on the source SQL instance — the ServiceManager database, and the Data Warehouse databases (DWStagingAndConfig, DWRepository, DWDataMart).
3. Restore the backups to the new SQL instance, matching SQL collation and edition requirements.
4. Update the Service Manager management servers to point at the new SQL instance/database names, using the registry keys and configuration Microsoft documents for this scenario (this step is version-specific).
5. Restart services and validate connectivity, console access, and Data Warehouse jobs before decommissioning the old SQL server.

Because the exact registry keys and supported steps have changed across Service Manager versions and cumulative updates, always check the current official Microsoft documentation for your specific version before starting, and take full backups (and ideally a test restore in a lab) before touching a production instance.

Still Supported in 2026

System Center Service Manager wasn’t dropped from the latest release — System Center 2025 Service Manager is still a fully supported product, with mainstream support running until January 2030 and extended support until January 2035. So this migration process remains current guidance rather than something being phased out; just make sure you’re checking Microsoft’s documentation for the specific version you’re running, since exact registry keys can still vary between releases.

Resources

• Migrate SCSM Database