Database limitations on number of projects in JIRA
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
This article describes known limitations imposed by various database servers on number of projects which can be created in JIRA.
Database | Limitation |
|---|---|
SQL Server | No hard limit as a query can have any number of parameters, as long as it remains within the maximum batch size — which defaults to 65,536 * Network Packet Size (256MB). In practice, however, 2000 is the limit as this is the maximum number of parameters allowed by SQL Server. (See |
PostgreSQL | No hard limits; SQL query size is limited to the OS maximum file size. |
Oracle | 1000 (Only for JIRA version prior to 6.1.1. See JRA-19317 for more details.) |
MySQL | No hard limit; maximum query size has to be less than max_allowed_packet, which defaults to 1GB, but can be any value in the range 1024-1073741824 Bytes. |
HSQLDB | HSQLDB is supported only for evaluation purpose only. No limits specified, but in practice limited by heap memory. |
