Technical Tip: Reducing Log File Sizes in FortiClient EMS by Changing SQL Server Recovery Model

[fatihseyligli]

Description	This article describes how to change the SQL Server recovery model to 'Simple' in FortiClient EMS on-premises deployments can reduce excessively large transaction log files, helping to prevent disk space issues while ensuring efficient database management.
Scope	FortiClient EMS on-premise.
Solution	In FortiClient EMS on-premises deployments, excessively large SQL Server transaction log files can occur when the database recovery model is set to 'Full'. Changing the recovery model to 'Simple' reduces log file size by automatically reclaiming space, which helps prevent disk space issues. This approach is recommended for environments where point-in-time recovery is not critical. The Full Recovery Model in SQL Server maintains a comprehensive log of all database transactions. While this model is essential for databases requiring point-in-time recovery, it can result in rapidly growing transaction log files.  For FortiClient EMS databases, this can become problematic if regular log backups are not taken, as the transaction log continues to grow until it is backed up. Resolution: To mitigate this issue, the SQL Server database recovery model for the FortiClient EMS database can be changed from 'Full' to 'Simple'. The Simple Recovery Model automatically reclaims log space to keep the transaction log file from growing excessively, making it suitable for scenarios where point-in-time recovery is not required. Steps to Change the Recovery Model to Simple: Open SQL Server Management Studio (SSMS). Connect to the SQL Server instance hosting the FortiClient EMS database. Locate the database. In the Object Explorer, navigate to 'Databases' -> 'FCM_Default' (or the relevant FortiClient EMS database). Access the database, 'right-click' the database (for example 'FCM_Default'), and select 'Properties'. In the database properties window, go to the 'Options' page. Under the 'Recovery Model' dropdown, select 'Simple'. Select 'OK' to apply changes. Best Practises: Adjust the backup strategy accordingly, as the 'Simple Recovery Model' does not support transaction log backups. Ensure that regular backups are taken to protect against data loss. Regularly monitor disk space usage to preempt any future issues related to database size.