Site announcement

We are switching off article comments on this website. Read about the upcoming changes to Atlassian Documentation.

Documentation for JIRA 6.4 (This documentation includes the project navigation sidebar). Not using this? See below:
(JIRA 6.4 without sidebar documentation | JIRA 6.3.x documentation | JIRA Cloud documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

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 HSQL database or an external database.

(info) JIRA's internal HSQL database is suitable for evaluation purposes. However, HSQL databases are prone to corruption. 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 PostgreSQL or MySQL 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.

The options for re-configuring your database connection depend on what JIRA distribution you are using:

'Recommended' distributions:

If you installed JIRA using the 'Windows Installer', 'Linux Installer' or from an 'Archive File', you can re-configure your database connection either with the JIRA Configuration Tool or manually.

WAR distribution:

If you have set up a JIRA WAR installation, you need to manually configure your database connection.

(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.

5 Comments

  1. Anonymous

    Is there plan to officially to support MariaDB?

  2. Anonymous

    We started using MariaDB officially, Can you please let us know Timeline for MariaDB official support?

    1. Hi there,

      We don't have plans to support MariaDB at this stage. Please vote/watch this ticket: JRA-32347 - JIRA should support MariaDB Open .

      Kind Regards,
      Andrew

  3. Really struggled getting this setup to mysql 5.5 on ubuntu.  Confluence connected just fine, but JIRA refused to connect to user@localhost identified by 'password'.   The only way it worked was to use wild cards on mysql grant syntax.  '%' was the only way it would bind.  Weird how confluence installed just fine using jira@localhost but JIRA itself woulnd't.

  4. I wish that Atlassian would take the trouble to update their application to use a non-ancient version of HSQLDB and correct their mis-statements about the HyperSQL.

    Yes, there could be corruption problems if there were a server crash with the 10-year-old hsqldb jar file that Atlassian is still using.  If they would simply update their jar to a recent HSQLDB version, update the mappings, and apply the "SET FILES WRITE DELAY 0" setting, they could deliver a top-quality ACID database not susceptible to corruption, and which would be ideal for permanent usage.  HSQLDB's built-in backup commands could be leveraged for automatic periodic backups.