Installation guide

Appendix B Transferring the
Configuration Database
Although the configuration database is created on a management server when
SystemProvisioning is installed, SQL Server 2008 R2 configured on a remote server on
the network also can be used. The following case is an example of creating SQL Server
2008 R2 Express Instance (Instance name: SSCCMDB) on a server that is not a
management server with the name, "SERVER1", and using the SQL instance as the
configuration database, which is described according to different authentication modes.
Transferring the configuration database from the management server to another server,
however, decreases performance of SystemProvisioning because SystemProvisioning
must frequently access to the remote configuration database.
Therefore, this procedure (transferring the configuration database) is not
recommended.
Note: You cannot setup the database of System Monitor - Performance Monitoring
Services on a server which is not a management server.
Using Windows Authentication Login
Perform the following procedures to transfer the configuration database when using the
Windows authentication login.
Note: Windows Authentication Login is valid only if SERVER1 joins the domain. If
SERVER1 joins the workgroup, use SQL Authentication Login.
1. Backing up SystemProvisioning
Back up SystemProvisioning.
For the procedure, see Subsection 10.2.1, "Backing up SystemProvisioning" in
SigmaSystemCenter Configuration Guide.
Note: Set the name of the backup file as "backup.dat".
2. Creating Instance
Setup the SQL Server 2008 R2 Express on the SERVER1.
1. Download the setup program of SQL Server 2008 R2 Express from the
following site.
http://www.microsoft.com/download/en/details.aspx?id=26729