To maintain optimal performance and prevent issues related to database size limitations, it is important to regularly maintain and monitor the SQL Server Express database in Trend Micro Deep Security Manager.
To ensure efficient SQL DB file housekeeping, we recommend following the steps below:
- Check the largest table in the Deep Security Database by opening SQL Server Management Studio, right-clicking on the Deep Security Database, selecting Reports > Standard Reports > Disk Usage by Top Tables.
- Check the pruning settings of the DSM Console and adjust the settings according to your preference by logging in to the DSM Console, navigating to Administration > System settings > Storage Tab.
- Check the SQL transaction logs by referring to this Microsoft article: Microsoft transaction log has grown to an extremely large size.
- Review the Log and event storage best practices. Customer environments with large retention requirements should rely on SIEM or Syslog server for log storage.
Please note that the current occupied space of the Trend Micro Deep Security Manager database file is not mentioned in the document. However, if the current occupied space of the SQL DB file is 400 GB, it is recommended to regularly prune the database to remove unnecessary data and free up space. For information on database pruning, see Log and event storage best practices.
To access the SQL DB file, navigate to SQLSERVER\MSSQL\Data\INDBmdf.
We hope this information helps. If you have any further questions or concerns, please do not hesitate to ask.