Migrating a Control Instance and Tenants to New Databases

For migrating 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. Restore the desired database backup file in SQL Server Management Studio (SSMS). 

Run the Decisions Installer, check the box for Change Settings on Update, and then select Update.

Select next until you get to the database setup step.

If migrating to an existing DB, point the ‘DB Database’ at the database being restored; the names need to match EXACTLY. If creating a new DB, choose a unique name that begins with a letter (ex: decisionsNEW).

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'

After resetting the password(s), the database should be accessible. The Control Instance is now set up on a different pre-existing database than before. 

Now, reinitialize the tenants by opening Settings.XML and changing the line reading ‘Server Type = Standard’ to ‘Type = Hosted’. Restart Service Host Manager to enable MultiTenancy.