Status: Closed (View Workflow)
Atlassian Update – 11 December 2018 Hi everyone, Thank you for your votes and thoughts on this issue. We fully understand that many of you are dependent on this functionality. After careful consideration, we've decided to prioritize adding Multi-Column Index to Jira Tables on Jira Server roadmap and already started development. To learn more on how you suggestions are reviewed, see our updated workflow for server feature suggestions. Kind regards, Jira Server Product Management
Some JIRA tables, like the propertyentry table contains many single column indexes, but many of the of SQL queries run by JIRA actually include checks for 2 or 3 of the columns.
propertyentry has indices on:
A majority of the SQL queries run against this table include:
- ENTITY_NAME, ENTITY_ID,PROPERTY_KEY
In these cases, it is left to the database to try and determine which index should be used, which is not always efficient. It may even cause extremely slow query times.
Add multi-column index to the table.
- Suggested index for Oracle:
- Suggested index for PostgreSQL:
- Suggested index for MSSQL: