Move to Production

This final migration step will switch your pilot database to production one last time. The configuration data of your pilot system will be unaffected.

During the final migration step, you can flip production databases, which means your old database will be taken offline, renamed to DatabaseName_SAVE, then the new Alloy Navigator 2024 database will take the name of the original database. This DatabaseName_SAVE database represents a backup of your Alloy Navigator data. We recommend that you keep the Flip Production Databases option enabled.

1. On the Task page, select Manage Existing Database option and click Next. The Source Database page opens.

2. Specify the information to connect to your production (source) database.

   1. Enter the name or IP address of the SQL server where your production database resides.

      NOTE: If you are connecting to a named SQL Server instance, it must be specified in the form Servername\Instancename; for example: SQLSERV001\SQLEXPRESS. If the server uses a non-standard port, add the port number, separating it with a comma; for example, SQLSERV001\SQLEXPRESS,5618.

   2. Provide your credentials to log on to the SQL Server using an account with the sysadmin role on the SQL Server:

      • To use your Windows account, choose Windows Authentication.

      • To use your SQL Server account, choose Standard Authentication and type your account name and password.

   3. Choose the name of the production (source) database from the drop-down list.

   
   Click Next. The Upgrade Scenario page opens.

3. Select Pilot Upgrade and click Next. The Pilot Upgrade page opens.

1. Run the Database Management tool for Alloy Navigator and click Next to continue.

2. Choose the Manage Existing Database option and click Next. The Source Database page opens..

3. Specify the information to connect to your production (source) Alloy Navigator Express database.

   1. Enter the name or IP address of the SQL server where your production database resides.

      NOTE: If you are connecting to a named SQL Server instance, it must be specified in the form Servername\Instancename; for example: SQLSERV001\SQLEXPRESS. If the server uses a non-standard port, add the port number, separating it with a comma; for example, SQLSERV001\SQLEXPRESS,5618.

   2. Provide your credentials to log on to the SQL Server using an account with the sysadmin role on the SQL Server:

      • To use your Windows account, choose Windows Authentication.

      • To use your SQL Server account, choose Standard Authentication and type your account name and password.

   3. Choose the name of the production (source) database from the drop-down list.

   
   Click Next. The Upgrade Scenario page opens.

4. Select Pilot Upgrade and click Next. The Pilot Upgrade page opens.

5. Select the Switch to Production option and click Next. The Switchover Options page opens.

6. Keep the Switch and Flip option selected and click Next. The Target Database page opens.

7. Select the name of your pilot (target) database and specify where to create a backup copy of the target database.

   Click Next. The Backup Location page opens.

8. Browse for a folder on the SQL server for the backup file and specify its file name. This upgrade step will not affect your production database, however, a backup copy is required for the process.

   Click Next. The Database Account page opens.

9. Specify the Database Account.

   INFO: For details, see Database Account.

   Provide the credentials for the SQL Server account that already serves as the Database Account for the pilot database. Alternatively, click Create SQL Server Account and create a new SQL Server account for this task.

   Click Next. The Database Access Key page opens.

10. The Database Management tool generates a Database Access Key. By default, the key is exported into the [KeyName].reg file on your desktop. To change the default path or name, click the ellipsis button and specify a new location.

    INFO: For details, see Distributing the Database Access Key.

    Click Next. The Ready to Proceed page opens.

11. Click Next to proceed, click Back if you need to make any changes.

12. Once the final database upgrade step completes, the Summary page opens with the information about the upgraded production database. Now you need to activate it. To start the activation, click Finish. The License Management window opens up.