Migrating From a Tenant Instance to a Standalone Database
- 16 Feb 2022
- 1 Minute to read
- Print
- DarkLight
Migrating From a Tenant Instance to a Standalone Database
- Updated on 16 Feb 2022
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Overview
Multi-Tenancy in v8 provides Administrators the flexibility and option to establish Tenant Instances from any desire locations. This may be completed by installing a new Version 8 Installation Tenant Instance from scratch, or by migrating a pre-existing standalone environment into a Hosted Tenant Instance.
Conversely, Tenant Instances can be migrated back into standalone databases. This allows Administrators the ability to detach a database from a Multi-Tenancy as desired/needed.
The following document demonstrates how to migrate a Tenant (Hosted) Database to a Standalone (Unmanaged) Database.
Example
- From the Local File System of the Standalone Database navigate to C:\Program Files\Decisions\Decisions Server and open Settings.xml in a Text Editor.
- From Settings.xml, change the value in between the <ServerType/> tags from "Hosted" to "Unmanaged".
- Save and close the Settings.xml.
- Right-click DecisionsServerInstaller.exe and select Run as administrator.
- From the Decisions Installer, select RESTART SERVICE.
- After the Decisions Service restarts, open and log into the Decisions Studio/User Portal for the respective database; verify that the Hosting Folder is no longer accessible via System.
Was this article helpful?