Documentation for JIRA 4.3. Documentation for other versions of JIRA is available too.

Skip to end of metadata
Go to start of metadata
Gliffy Zoom Zoom

JIRA requires a relational database for storage of issue data.

The time at which you connect JIRA to a database depends on whether you are using the JIRA Standalone distribution or the JIRA WAR/EAR distribution:

JIRA Standalone:

As part of its installation process, JIRA Standalone automatically installs, configures and connects itself to an HSQLDB database. This is fine for evaluation purposes, however HSQLDB is prone to database corruption. For production installations, we strongly recommend that you connect JIRA Standalone to an enterprise database. This also lets you take advantage of existing database backup and recovery procedures.

JIRA WAR/EAR:

When you install JIRA WAR/EAR, you will need to manually configure your database connection.

The following instructions apply to both JIRA Standalone and JIRA WAR/EAR:

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.

Icon

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

Data migration

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