User Problem

The current implementation of tblAuditLog in Jira Align (JA) handles all logging without a mechanism to control table growth. There is no archiving process, which can lead to significant performance issues. As the table grows, it can cause locks and other performance-related problems.

Additionally, other tables, such as tblAgileStoryAudit, also experience excessive growth, further exacerbating performance issues and increasing the complexity of managing log data.

Suggested Solutions

To address the issues with tblAuditLog and other large tables, we suggest the following solutions:

• Implement SQL Table Partitioning: Partitioning the tblAuditLog and similar tables can help manage their size by dividing them into smaller, more manageable pieces. This can improve performance by reducing the load on any single partition and making maintenance tasks more efficient.
• Introduce an Archiving Process: Implementing an archiving process will allow old log entries to be moved to a different storage solution, freeing up space in the primary log tables and ensuring that only relevant data is actively managed.

Current Workarounds

Currently, there are no effective workarounds in place to control the growth of tblAuditLog and other large tables. Users have reported performance issues due to the large sizes of these tables, and manual efforts to manage the data have proven insufficient. Without a structured solution like partitioning or archiving, these tables will continue to grow unchecked, exacerbating the existing performance problems.