You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
On my JIRA instance (v5.2.11) I have some performance issues.
DBAs detect that this SQL request is slow :
SELECT CG.ID, CG.issueid, CG.AUTHOR, CG.CREATED, CI.ID, CI.groupid, CI.FIELDTYPE, CI.FIELD, CI.OLDVALUE, CI.OLDSTRING, CI.NEWVALUE, CI.NEWSTRING FROM dbo.changegroup CG INNER JOIN dbo.changeitem CI ON CG.ID = CI.groupid WHERE CG.issueid= @P0 ORDER BY CG.CREATED ASC, CI.ID ASC
Because of 12million of line in table "changeitem".
Is it possible to archived or purge this table ?
Is it possible to partitioning with statistical incrementalism ?
Removing lines from this tables destroys some of your issue data, so that should not be done. (Plus you'll need to be doing related deletes, the table has relationships with a number of other things and you need to be really careful not to end up with an unusable Jira due to data corruption)
Partitioning is not supported by Jira, if you can do it at a database level and have no apparent effect on the SQL it needs to run, that's fine, but the application won't do it.