Introduction

IMPORTANT: The use of a Central Database is recommended as of PrizmDoc v14.4. If you are using PrizmDoc v14.1-v14.3, a database is required and PrizmDoc will not start without a valid MySQL connection string. For a complete list of database recommendations, refer to the Database Recommendations topic.

A database must be provided in order to use viewing packages. You can see a list of supported databases in the PAS Configuration topic. If you start up PAS against a new database, PAS will automatically create the necessary tables.

We recommend you create a dedicated database for PrizmDoc and a restricted database user that only has permissions for this database. Make sure the PrizmDoc user has all privileges to this database.

Maintaining the Database

While directly reading, linking, or otherwise using the data stored in the database by PAS is discouraged, you will still need to do regular administrative tasks, such as taking proper snapshots and backups of the data in order to prevent and mitigate data loss.

In the event of data loss that requires recovery from a backup (both for the database or the local file storage) PAS has an API to validate viewing packages and their state. For more information, refer to the Viewing Packages API.

Product and Database Updates

As the Pre-Conversion (Viewing Packages) feature is updated in future releases, the product will contain the necessary logic to transition existing tables and data to the new format, if a schema change is necessary.