Connecting JIRA applications to a database

JIRA requires a relational database to store its issue data.

If you are setting up a completely new JIRA installation, the JIRA setup wizard will configure a database connection for you to either JIRA's internal H2 or an external database.

(info) JIRA's internal H2 database is suitable for evaluation purposes. For production installations of JIRA, we strongly recommend that you connect JIRA to another supported database. This allows you to take advantage of your database system's own backup and recovery features.

The following are more detailed instructions for configuring a connection to a JIRA database:

Which database?

Your choice of database can significantly affect your subsequent experience of JIRA administration. If you have a choice of databases, please first read our list of supported databases.

If you are looking for a low-cost solution, consider using MySQL or PostgreSQL, as both of these are open source (free) software.

Upgrading JIRA or migrating JIRA to another server?

If you are upgrading JIRA manually or migrating JIRA to another server, and do not have access to a pre-existing dbconfig.xml file, you will need to re-configure your database connection. This results in a dbconfig.xml file (being created in the JIRA home directory of your new JIRA installation), whose content defines your JIRA database connection.

You can re-configure your database connection with either the JIRA configuration tool, or you can do it manually. 

(tick) Specific instructions for configuring database connections, either using the JIRA configuration tool or manually, are provided in the specific instructions for each database (listed above).

Data Migration

To transfer your issue data from one database to another, please refer to the instructions for Switching databases.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport