The internal PaperCut database is stable, scalable, self-maintaining and provides very good performance. For this reason most organizations do not need to run PaperCut on an external database system. However there are some good reasons to run PaperCut on an external RDBMS, including:
PaperCut NG and PaperCut MF share a common database schema. Organizations running PaperCut on an external database system such as Microsoft SQL Server, PostgreSQL, MySQL or Oracle may find the following schema diagrams useful when designing custom SQL queries and reports. If you need assistance or advice writing an SQL query please contact support.
By default PaperCut stores its data in an internal database format that is not accessible for external reporting. To access the database for reporting, PaperCut must be running on an external database. Instructions for moving to an external database can be found in the manual here: http://www.papercut.com/products/ng/manual/ch-ext-db.html
Where possible we strongly recommend read-only data access. Any modifications should be done either via the PaperCut interface, or via the XML-Web Services API. Direct database manipulation outside PaperCut 'may' lead to data inconsistencies - for example, transactions logs not matching account balances.
Database administrators or query developers may also find the SQL database creation scripts useful. These present the schema in standard SQL create statements. The scripts are located in sub directories of: [app-dir]/server/lib/sql
If you have any questions about the DB Schema, or data access in general, please contact our support team.