* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Database Schema Diagrams
Tandem Computers wikipedia , lookup
Global serializability wikipedia , lookup
Commitment ordering wikipedia , lookup
Entity–attribute–value model wikipedia , lookup
Serializability wikipedia , lookup
Extensible Storage Engine wikipedia , lookup
Microsoft Access wikipedia , lookup
Functional Database Model wikipedia , lookup
Ingres (database) wikipedia , lookup
Oracle Database wikipedia , lookup
Microsoft SQL Server wikipedia , lookup
Open Database Connectivity wikipedia , lookup
Concurrency control wikipedia , lookup
Versant Object Database wikipedia , lookup
Microsoft Jet Database Engine wikipedia , lookup
Relational model wikipedia , lookup
Database model wikipedia , lookup
Why use an external RDBMS? 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: Your organization has existing database infrastructure and would like to consolidate all applications on the same database platform. Your organization has an existing database maintenance and backup procedure and would like PaperCut to take advantage of this. People would like to use 3rd party reporting and analysis tools (like Crystal Reports or Microsoft Access) to view and analyze the PaperCut database. Your organization is very large and requires the performance benefits of a dedicated RDBMS. This also allows the database to reside on a separate server to PaperCut, which improves the system scalability. Supported database servers: Self-managing internal database: suitable for up to 5,000 users Microsoft SQL Server 2000/2005/2008 (either 32 or 64 bit) Microsoft SQL Express 2005/2008 (free from Microsoft) PostgreSQL 7.1+ (a free open source database) MySQL 5.0+ (a free open source database) Oracle 9.2+ (including the free Oracle Express Edition). 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, 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. PaperCut Database Schema Revision-22 (PDF) Updated: 24th Apr 2010 PaperCut Database Schema Revision-27 (PDF) Updated 13th Sept. 2011 - Version: 11.4 (Build 14550) 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.