Upgrading and migrating Control Center to another server

You can migrate your existing Control Center10 to a new server or you can migrate your Control Center 2019 and perform an upgrade to 10.

Warning

Control Center10 database is not compatible with the previous versions of Control Center. You can't revert to the previous versions of Control Center once you upgrade the database. Create your Control Center database backup before you upgrade to Control Center10.

Migrating to a new server consists of two steps:

Migrating of Control Center database.
Installing the Control Center application on your new server.

You can install the Control Center application and database on the same server or on separate servers.

When you migrate your database to a new server, some existing database settings prevent your new Control Center installation to work. The following procedure describes also how to change the necessary database properties to enable your new Control Center.

The goal is to copy your existing database to your new server and enable new users by running SQL scripts.

If you have currently installed Control Center V2019, activate your LMS10 license key in your existing Control Center. Control Center V2019 works also with the V10 license.

To migrate your Control Center database and upgrade your Control Center:

On your current server create your Control Center SQL database backup. Copy the database backup to your new server and perform a database restore.
Install Control Center10 on your new server. During the installation select a database name that is different than the name of your backup database from your old server. (The default database name is NiceAN which is in most cases also the name of your old database. So during the installation select for example NiceAN1 name).

Warning

Carefully check the option to enable HTTPS. You can't change the option after the installation without reinstalling Control Center.

The installation creates Windows users EPM_USER and EPM_DB_ADMIN.

The steps 3. - 7. describe how to set up EPM_USER and EPM_DB_ADMIN users.
Open your SQL Management Studio and run the script to create Windows or SQL credentials on the old database (the database restored from your old server).

Warning

Edit the scripts before executing. Replace variable names $(VARIABLE_NAME).
```
USE [master];    
GO
```

Add permissions to EPM_DBADMIN user:

GRANT CONNECT SQL TO [$(EPM_DB_ADMIN)];
GRANT CREATE ANY DATABASE TO [$(EPM_DB_ADMIN)];

Create EPM_USER and grant permissions:

USE [$(DatabaseName)];
GO
CREATE USER [$(EPM_USER)] FOR LOGIN [$(EPM_USER)] WITH DEFAULT_SCHEMA = [$(SchemaName)];
GRANT CONTROL, EXECUTE, SELECT, INSERT, UPDATE, DELETE ON SCHEMA::[$(SchemaName)] TO [$(EPM_USER)];
GRANT CREATE TABLE TO [$(EPM_USER)];
GRANT CREATE SCHEMA TO [$(EPM_USER)];

Change the owner of SignalR schema:

IF EXISTS (SELECT * FROM sys.schemas WHERE name = 'SignalR')
BEGIN
     -- set schema owner
        EXEC ('ALTER AUTHORIZATION ON SCHEMA::[SignalR] TO [$(EPM_USER)];');
END

Change the owner of the database. Here is the syntax for Windows users:
```
EXEC ('ALTER AUTHORIZATION ON DATABASE::[$(DatabaseName)] TO [$(EPM_DB_ADMIN)];');
```
Note

$(DatabaseName) replace with NiceAN (your old database)

$(SchemaName) replace with nan

$(EPM_DB_ADMIN) replace with NEW_SERVER\EPM_DBADMIN

$(EPM_USER) replace with NEW_SERVER\EPM_USER
Rename your newly installed database, then rename your backup database to the name of your newly created database before renaming. This way your Control Center will use your backup database with new users.

Example 1. Example

Your backup database name is NiceAN. When you installed your new database, you selected the name NiceAN1.

First, you rename your newly installed database from NiceAN1 to NiceAN1a.

Then you rename your backup database from NiceAn to NiceAn1.

Note

You can rename your databases if they are offline. Right-click your database and select Tasks > Take Offline.

Now you can run Control Center on your new server.

Warning

Warning

Warning

Note

Note