To benefit from the latest LPR database improvements in Security Center 5.7, you'll need to migrate your existing LPR data to the new database structure.
Upgrade your system to Security Center 5.7 SR2.
Before you begin
What you should know
- The LPR database improvements were released in Security Center 5.6 SR1. This procedure applies to systems upgrading from Security Center 5.6 GA and earlier to Security Center 5.7 SR2.
- Starting from Security Center 5.6 SR1, license plate reads and hits are decoupled from the LPR images (license plate, context, and wheel images). As a result, the LPR Manager can store up to 6 millions reads in the SQL Express database, which is 25 to 30 times more reads than before. The responsiveness of the LPR reports is also improved because of database enhancements and the lazy loading of report images in Security Desk.
- You can migrate the database while the system is in operation; however, we recommend that you perform the migration outside of peak usage hours. Depending on the size of the database, the amount of image data to migrate, and the performance of the Archiver disk, the database migration can take from several hours to several days to complete.
- If the system includes more than one LPR Manager role, we recommend that you migrate one LPR Manager at a time. Upgrading in increments does not affect system functionality.
- While the migration is in progress, you can edit reads that were collected after
SR2 upgrade.WARNING: Do not attempt to edit or protect old reads and hits (pre-upgrade) until the migration is complete. If you must edit or protect an old read, you can temporarily stop the migration.
- Database cleanup and housekeeping is only done after the database has been migrated and validated.
- You can stop and restart the
migration without losing data. For example, you might need to stop
the migration if you are experiencing performance issues while migrating the
database on a live system and you prefer to perform the migration in stages each
night.WARNING: If you experience problems during the migration, you can restart the migration, but do not restore the database. If the system is in operation during the migration, restoring the database causes the loss of all new LPR data that was added after the migration started.
Back up the LPR database for each LPR Manager role.
- From the Config Tool home page, open the System task, and click the Roles view.
- Select an LPR Manager role, and click Resources.
- In the Actions section, click Database update () .
- In the Actions section, click Backup/Restore ().
- Back up the Directory database.
Assign a unique logical ID to each of the LPR Managers in the system. The
logical ID is used to reference the LPR Manager role for the migration
WARNING: After the migration starts, do not change the logical ID until the migration is complete.
- Open the LPR task, and select Roles and units.
- Select an LPR Manager.
- In the Identity tab, enter a Logical ID.
- Click Apply.
Launch the database migration.
The system starts the migration on the selected LPR Manager role.
- Start the Security Center Server Admin () application.
Enter the server password that you set during the server installation,
and click Log on.
The Server Admin Overview page is displayed.
- Select your server from the Servers list.
- From the Actions drop-down list, select </> Console.
- Select the Commands tab.
- From the commands list, expand License Plate Management commands and select Start SC 5.6 Database Migration. The Enter parameters window is displayed.
- Enter the logical ID of the LPR Manager role whose database you want to migrate.
In the writeTrueToStartMigration field, type
true and click
To view the progress of your database migration in Server Admin, from the commands list, expand License Plate Management commands and select Database Migration Status. Enter the logical ID of the LPR Manager role whose database you are migrating, and then click OK.