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 database, and deciding which database can be a difficult task.
PaperCut has a number of supported external databases that can be used with your PaperCut installation. One of our more popular questions we get asked when deciding to use an external database is which one?
What are you most comfortable using?
PaperCut does not have a preference of external databases that should be utilized, and a large factor in deciding what external database you should use depends on your current knowledge of database administration. If you are already familiar with a family of database backends such as Microsoft SQL Server, PostgreSQL, or Oracle, then it would be best for you to use these for your new external database.
Other minor factors to consider here are,
- Are you familiar with the maintenance of this database?
- Will you know how to run your own internal custom reporting using our database schema?
Do you have an existing database infrastructure you can use?
If you have an existing database infrastructure already in place, you should look at incorporating the PaperCut database into it. This means you’re bundling multiple factors, including:
- Previous knowledge
After these considerations, it’s time to deploy your external database.
Categories: Databases, Architecture
Keywords: SQL Server, PostgreSQL, MySQL, Oracle, Schema, RDBMS, Apache, Derby, Deployment