Documentation for JIRA 4.3. Documentation for other versions of JIRA is available too. 
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:
- Connecting JIRA to MySQL
- Connecting JIRA to PostgreSQL
- Connecting JIRA to SQL Server 2005
- Connecting JIRA to SQL Server 2008
- Connecting JIRA to Oracle
- Connecting JIRA to HSQLDB
- Switching Databases
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.
Data migration
To transfer your issue data from one database to another, please refer to the instructions for Switching databases.
Overview
Content Tools
Apps
See our Getting Help page for details.
Raise an issue for our developers.
See answers from the community.
Tweet, blog and update our documentation.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.