• Article

Appendix B - Guidance for Moving the Service Manager and Data Warehouse Databases

 

Updated: May 13, 2016

Applies To: System Center 2012 SP1 - Service Manager, System Center 2012 R2 Service Manager, System Center 2012 - Service Manager

After you have deployed Service Manager, you might need to move the Service Manager or data warehouse databases from one computer running Microsoft SQL Server to another for reasons such as the following:

  • You need to replace hardware that is experiencing issues and that is no longer considered reliable.

  • You need to add additional hardware to improve scalability and performance.

  • You need to move a database and log file to a different volume because of space or performance reasons.

  • You need to change hardware that is leased and is due to expire soon.

  • You need to change or upgrade hardware to comply with new hardware standards.

  • You initially installed multiple Service Manager components on a single server, and you need to distribute some components to other servers.

  • You need to restore functionality in a failure scenario.

If you want the move the data warehouse database, and if you have installed Service Manager within the last 90 days, it might be easier for you to unregister the data warehouse, install a new data warehouse, and register the new database. If the data has not been groomed from the Service Manager database, there will be no data loss in the data warehouse database because it will be synchronized. By default, the grooming interval for work items is 90 days from the last time a work item was modified. Using this process is much simpler than using the following guidance, which details how to move your databases from one server to another and requires many steps.

Moving databases

For procedures about how to move databases from one computer running SQL Server to another, see the following topics:

See also