JIRA requires a relational database to store its issue data.
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 instructions for configuring a connection to a JIRA database apply to both the JIRA Standalone and WAR distributions:
- Connecting JIRA to PostgreSQL
- Connecting JIRA to MySQL
- Connecting JIRA to Oracle
- Connecting JIRA to SQL Server 2005
- Connecting JIRA to SQL Server 2008
- Connecting JIRA to HSQLDB
- Switching Databases
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.
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:
When you install JIRA WAR, you will need to manually configure your database connection.
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).
To transfer your issue data from one database to another, please refer to the instructions for Switching databases.