There are 3 ways one can upgrade from an older version (v2016.2 or v2017.1) of Orchestrator, and migrate the database:
- Using the Scripts - suitable for a one node or multi-node architecture. An in-place upgrade that copies all your settings and creates a backup folder for the old version. This is the recommended method of upgrading.
- Using the Windows Installer (
UiPathPlatform.msi) - suitable for a one node architecture. Please note that some
web.configsettings are not copied if the version you are upgrading from was installed using scripts. Please note that the repair functionality of the Windows Installer is not supported.
- Using the Azure Script - a complex upgrade of Orchestrator and its components on one or multiple nodes, in the Azure Portal.
Regardless of the way you choose to upgrade, please note that if the database you point to does not exist, it is automatically created while running the upgrade. If you point to an existing database, it is upgraded during the same process.
The Orchestrator SQL database is automatically set to be case-insensitive (“OrchDB” = “orchdb”).