Connecting Jira applications to a database
Jira requires a relational database to store its issue data. If you're 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.
Below you can find more detailed instructions for connecting Jira to a database:
- Connecting Jira Data Center to Amazon Aurora
- Connecting Jira applications to Azure SQL
- Connecting Jira applications to PostgreSQL
- Connecting Jira applications to MySQL 8.0
- Connecting Jira applications to Oracle
- Connecting Jira applications to SQL Server 2017
- Connecting Jira applications to SQL Server 2019
- Tuning database connections
- Encrypting database password
- Connecting Jira applications to MySQL 5.7
- Connecting Jira applications to Pgpool-II
- Switching databases
- Connecting Jira applications to SQL Server 2016
Which database?
Your choice of database can significantly affect your subsequent experience of Jira administration. If you have a choice of databases, 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 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 manually by editing the dbconfig.xml file. You can find the details on how to do it 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.
Known issues
The following table lists known issues that might occur during the database operation or the execution of database procedures. We are aware of these issues and have planned their resolution in future releases.
| Database | Issue | Solution |
|---|---|---|
| SQL Server | The database doesn't allow more than 2000 parameters in a query. | This is a known limitation set by SQL Server. According to SQL Docs, a procedure can have a maximum of 2100 parameters. The issue is tracked in the ticket JRASERVER-63290 - Getting issue details... STATUS Feel free to leave comments on the ticket so we know your use cases better and understand how this issue is impacting your operations. |