Introduction

NOTE: Use of a Central Database for PrizmDoc will be required in order to move towards eliminating server affinity.

A database must be provided in order to start PAS. You can see a list of supported databases in the PAS Configuration topic. After configuring PAS with the correct information, some databases, like Microsoft SQL Server, will require that a script is run in order to set up the correct tables for that database. This is normally done at PAS start up, but if you want to run the script manually, refer to the running the database scripts topic. Please note that PAS itself will normally only require read/write access to the database, but during startup will require access to create and migrate tables.

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 or scripts to transition existing tables and data to the new format, if a schema change is necessary. You can find out more information on updating PAS in the topic for setting up your database.