There are several SQL specific configurations and server settings that can affect performance and operation.
Avoid deploying the Audit Store databases in a SQL availability group unless it’s required by the company’s compliance policies.
Configure SQL Server power settings to be set to Balanced instead of High Performance.
SQL Server has a setting called Max Server Memory that controls the maximum amount of physical memory that can be consumed by the SQL Server’s buffer pool. An incorrectly configured Max Server Memory may either result into the SQL engine causing high IO or OS/other programs starving for more memory. Refer to the “configuring the maximum memory for audit store databases” section of the and always configure this value as recommended before the deployment begins.
If you’re expecting a database server to get migrated/retired in the near future, it’s better to create a CNAME alias in DNS for the current database server and specify the alias everywhere (e.g. when creating a new Management database) rather than specifying the actual host name. This will prevent scenarios where the database server is not found after a migration.