Table of Contents
This section describes the process of running PaperCut MF on an external relational database, and describes why an organization would choose to do this. By default PaperCut MF uses an internal database product known as Apache Derby. This database engine was donated to Apache by IBM and was previously known as IBM Cloudscape.
The internal PaperCut MF database is stable, scalable, self-maintaining and provides very good performance. For this reason most organizations do not need to run PaperCut MF on an external database system. However there are some good reasons to run PaperCut MF 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 MF 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 MF 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 MF, which improves the system scalability.
PaperCut Software International Pty Ltd supports the following external databases out-of-the-box:
Microsoft SQL Server 2000/2005/2008/2012 (either 32 or 64 bit)
Microsoft SQL Express 2005/2008/2012 (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).
These databases were chosen to cater for the majority of our customers. For more information on supported databases, see the External Database Support Policy.
© Copyright 1999-2014. PaperCut Software International Pty Ltd. All rights reserved.