If you are upgrading from Security Center 5.6 GA or earlier to 5.8, you must migrate your existing LPR data to the new database structure.
Before you begin
IMPORTANT: The LPR database migration is not
compatible with Microsoft SQL Server 2016 and later. Before attempting the
migration, ensure that you are running an earlier version of SQL Server. The
following database engines are supported:
- SQL Server 2008 R2 Express/Standard/Enterprise
- SQL Server 2012 Express/Standard/Enterprise
- SQL Server 2014 Express/Standard/Enterprise
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.8 GA.
- 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 Server 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
the Security
Center
5.8
GA upgrade.CAUTION: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.CAUTION: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.