The Connecting Jira applications to SQL Server 2017 document mentions regular database maintenance tasks as below:

Schedule regular database maintenance tasks 

To achieve and maintain optimal MS SQL performance, schedule daily maintenance tasks to update database statistics.

Schedule a daily maintenance task for hot tables

Hot tables are the most active tables in your database. For example, propertyentry, changeitem, and changegroup are large data tables that are used frequently and require regular updating of statistics.

To set up a daily maintenance task for hot tables, run the following command:

UPDATE STATISTICS <table.name>

Schedule a weekly maintenance task for the whole database

To set up a weekly maintenance task for the whole database, run the following command:

 {{UPDATE STATISTICS <table.name> with fullscan}}
 

For large databases, updating statistics with fullscan might take a long time to complete. To minimize the impact on your production environment, schedule this maintenance task for off-peak hours.

For more information on how to update MS SQL Server statistics, see the official Microsoft documentation.

While we have similar recommendation on the Connecting Jira applications to Azure SQL documentation, we are missing these from the following documents:

• Connecting Jira applications to SQL Server 2022
• Connecting Jira applications to SQL Server 2019

We should consistently add these recommendations on any Connecting Jira applications to <MS SQL Server|Azure SQL Server> product document.