Running PaperCut On An External Database

KB Home   |   Running PaperCut On An External Database

Main.RunningPaperCutOnAnExternalDatabase History

Hide minor edits - Show changes to output

Changed line 9 from:
* You want to run SQL queries on the PaperCut database, for instance in order to create custom reports. Note: Do not update the PaperCut database with SQL statements.
to:
* You want to run SQL queries on the PaperCut database, for instance in order to create custom reports. Note: Do not update the PaperCut database using SQL.
August 30, 2017, at 09:08 PM by Alec - Added some reasons to use external database.
Added lines 4-9:

Reasons for using an external database include:

* Your system is now sufficiently big that an external database improves performance. For some guidelines see https://www.papercut.com/kb/Main/PaperCutServerSizingGuide
* You already have a database infrastructure and you want PaperCut to be managed the same way as your other databases
* You want to run SQL queries on the PaperCut database, for instance in order to create custom reports. Note: Do not update the PaperCut database with SQL statements.
December 21, 2010, at 11:47 PM by Rick - clarified db location options
Changed lines 3-4 from:
By default PaperCut uses an internal embedded database called Apache Derby which was initially developed by IBM and sold as Cloudspace DB.  PaperCut can also be run on external databases like Microsoft SQL Server (including the free Express Edition), [=PostgreSQL=], My SQL or Oracle.
to:
By default PaperCut uses an internal embedded database called Apache Derby which was initially developed by IBM and sold as Cloudspace DB.  PaperCut can also be run on external databases like Microsoft SQL Server (including the free Express Edition), [=PostgreSQL=], My SQL or Oracle. The external database can be hosted on the PaperCut Primary server or on a separate server.
Changed lines 5-6 from:
For more information using an external database, and instructions on how to "upsize" to and external database, see the [[https://www.papercut.com/products/ng/manual/ch-ext-db.html | manual here]].
to:
For more information using an external database, and instructions on how to "upsize" to an external database, see the [[https://www.papercut.com/products/ng/manual/ch-ext-db.html | manual here]].
Changed lines 3-4 from:
By default PaperCut uses an internal embedded database called Apache Derby which was initially developed by IBM and sold as Cloudspace DB.  PaperCut can also be run on external databases like Microsoft SQL Server (including the free Express Edition), [=PostgreSQL=] or Oracle.
to:
By default PaperCut uses an internal embedded database called Apache Derby which was initially developed by IBM and sold as Cloudspace DB.  PaperCut can also be run on external databases like Microsoft SQL Server (including the free Express Edition), [=PostgreSQL=], My SQL or Oracle.
Added lines 1-10:
(:title Running PaperCut On An External Database:)

By default PaperCut uses an internal embedded database called Apache Derby which was initially developed by IBM and sold as Cloudspace DB.  PaperCut can also be run on external databases like Microsoft SQL Server (including the free Express Edition), [=PostgreSQL=] or Oracle.

For more information using an external database, and instructions on how to "upsize" to and external database, see the [[https://www.papercut.com/products/ng/manual/ch-ext-db.html | manual here]].

For information on supported external databases, see the [[ExternalDatabases | external database support policy]].


''Categories:'' [[!Databases]]

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on August 30, 2017, at 09:09 PM
Printable View   |   Article History   |   Edit Article