Migrating a Control Instance and Tenants to New Databases

Example

To migrate to an existing database, use the reference articles below to get started on restoring the database. For creating a new database, skip to the Decisions Installer instructions.

Use this Solarwinds article for information on restoring a .bak file or this Microsoft article for information on restoring a .bacpac file.

From the File System, restore the desired database Backup file in SQL Server Management Studio (SSMS).

Run DecisionsServerInstaller.exe.

Check the Change Settings on Update box, then click UPDATE.

Proceed through setup until the Database Setup step is reached; if migrating to a pre-existing database, match the DB Database to the exact name of the database being restored. If creating a new database, choose a unique name that begins with a letter.

Reset the Admin Account.

Resetting the Admin Account may require running the Emergency Password Reset Tool. The "admin@decisions.com" account can be reset from the database backup since it exists in most instances. If this does not work, navigate to SSMS and run the following Query to determine what Admin Account to reset.

select ea.email_address, eg.entity_name, ea.authentication_type, ea.can_use_portal,ea.is_active, * from entity_account as ea
join account_group_join as agj on ea.account_id = agj.account_id
join entity_group as eg on eg.group_id = agj.group_id
where eg.entity_name = 'Administrators' and ea.authentication_type = 'Password'

Resetting the password will allow access to the database; the Control Instance is now set up on a different database than before.

Reinitialize Tenants by opening Settings.xml in a text editor, locate the <ServerType> tag, and change the value from Standard to Hosted; Save then Exit the file.

Open DecisionsServerInstaller.exe, and select RESTART SERVICE to finish enabling the Multi-Tenant environment.

Migrating a Control Instance and Tenants to New Databases

Overview

Example

What's Next