Database Migration Tool - Use and Best Practices
The Database Migration tool is used to migrate Printers, Users, Client Custom Fields and Jobs from a Print Audit 6 database to a User Management database.
We highly recommend engaging our Professional Services team when moving from Print Audit 6 to User Management but if you elect to do it yourself, then the best practices included in this article will help minimize any errors that may occur in the Database migration:
We highly recommend engaging our Professional Services team when moving from Print Audit 6 to User Management but if you elect to do it yourself, then the best practices included in this article will help minimize any errors that may occur in the Database migration:
- Make sure the Print Audit 6 server backend is upgraded to at least 6.14. Don't try to migrate from an older version of PA 6.
- On the UM server, shutdown IIS to block any other connections to the UM database. Don't try the migration when UM making live connections to the database.
- Keep the number of jobs being migrated to a minimum. The more jobs you try to migrate, the greater the chance that a job in PA 6 is going to cause the migration to fail. “No jobs” is best.
- If dealing with a large customer database with a lot of job data, try a month's worth of job data as a test first. Expand the jobs window only if the test works.
If you looking to use the Database Migration tool:
- Login to the User Management server. Locate the UM Release and Task Services in Windows Services. Stop both services before starting the migration.
- Launch the Database Migration Tool under User Management on the server UM has been installed on:
- Select type of Print Audit 6 database - Access or SQL server. (The database type can be determined in the Print Audit 6 Administrator by going to Tools --> Set Database). Click Next.
-
Access - you'll need the location of the pa6db.mdb file. Browse to the location, select the file and click Next.
-
SQL Server - you'll need the Server/Instance, user and password used for the PA 6 database. Click Next.
- You'll need to put in the Server/Instance and Database name, login and password of the User Management.
- 5. Once authenticated to the UM database, choose whether to migrate all jobs, no jobs or jobs after a certain date. In addition to jobs, the Database Migration Tool will migrate Client Custom Fields, Printers and Users.
- If the database migration is successful, restart IIS (if it was stopped) and the User Management services (Release and Task).
How did we do with this article?