Pilot Upgrade / Pilot Testing
Updated in 2023.1
Microsoft SQL Server only
The pilot upgrade or pilot testing is a multi-step process. Select the step you are at and click Next.
Create Pilot Database
This step imports all your data, including the configuration information and data records, from your existing production database to a new database of the latest version. Then you use that new database as a pilot database for configuring and initial testing while still using your existing database in production
Update Pilot Data
During the process of configuring and testing you may want to update your pilot database with the most recent records from the production database. This will show how your production data looks in your new environment. This step does not import an configuration information from the production database, only data records.
The "Update Pilot Data" step is optional. You can repeat it as many times as you want.
Switch to Production
This is the final step. Take it when you have a fully configured and tested pilot database and are ready to begin its production use. This step will replace all data records (such as tickets, knowledge base articles, computers, etc.) in the pilot database with your latest production data one last time.
NOTE: The "Switch to Production" step does not import an configuration information from the production database, only data records, so any configuration changes made to your existing production system after creating the pilot database will not be reflected.
NOTE: If you are upgrading from Alloy Navigator 7.2 or later, the final step also turns the Automatic Upgrade on. This feature helps distribute the latest client components among your technicians. For details, see Enabling Automatic Upgrade.