Important pretest before database migration

IT Asset Management version 2018 R2
Tip: If you are using a cloud implementation of IT Asset Management, skip this topic, as this work is already managed on your behalf.
If you are upgrading your on-premises implementation from an earlier release of IT Asset Management to 2024 R1.1, it is important to note that any data currently in your FlexNet databases that violate underlying database constraints will now cause your database migration to fail, bringing your upgrade to a halt. This increased rigor is being applied because, after previous upgrades, cases were found of customer data that had been inserted in violation of constraints, and these produced compliance errors in subsequent operations. All of the following databases are now subject to this constraints check, which also reactivates any disabled constraints:
  • Compliance database (default name FNMSCompliance)
  • Inventory database (default name FNMSInventory)
  • Data warehouse database (default name FNMSDataWarehouse).
In order to avoid such failures during migration, it is important first to run a new database script against each of these databases in turn. The script identifies constraints that must be honored, and outputs an SQL statement for each case. You then copy the SQL statements and run those customized statements against your databases. If there are any database constraint violations, an alert is output that looks like this:
Data exists in dbo.tableName which will break foreign key FK_name
Hopefully, in your databases there are no such cases, and you can proceed with the database upgrade. However, if you do see such alerts in this test, on any of the above databases, the errors must be corrected before you can proceed with the upgrade. Your database administrators may wish to check the Schema Reference PDF for further insights into the constraints; but in general, best practice is to raise a support ticket to have Flexera experts assist in cleaning up any problematic data.
The necessary database script to run as an advance check on your current databases is available:

Additional information

Consultants: If you have your own customized scripts and processes for completing upgrades for customers, be warned that these will break in any case where existing data violates database constraints. Be sure to collect your own copy of the database script, and validate existing data in all relevant databases before running your own process/script.

IT Asset Management (Cloud)

Current