Database Schema Diagrams
PaperCut NG and PaperCut MF share a common database schema. Organizations running PaperCut on an external database system such as Microsoft SQL Server, PostgreSQL, or Oracle may find the following schema diagrams useful when designing custom SQL queries and reports.
For example SQL queries, you can find a detailed run-through of building custom reports with Crystal Reports as an example. Additionally you can refer to the repository of the SQL queries used in the PaperCut reports as starting points for your customized queries.
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: https://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.
Schema Diagrams: Up-to-date since 2nd June 2020 - Version 20.0.0
Note: Site-Servers have the same schema as the Primary Server.
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:
If you have any questions about the DB Schema, or data access in general, please contact our support team.
keywords: direct data, odbc, jdbc, database drivers, table structure, data base layout, fields