The database log file is too large to clean up （sqlserver）

[ourlang]

1、Connect to the database and configure it as SQL Server
2、The validity period of the log is set to 2 days

3、There are three tables in the database that take up a lot of space and cannot be cleaned up
D_MC1 、D_MM1,D_M1

4、How to make scheduled cleaning of logs and database files effective

[pacmano1]

Most folks prune every hour. Your frequency likely can't keep up.

[ourlang]

In addition to setting up here data prune , please Is there any other way to reduce the disk space occupied by large database files or to regularly clean up database files？

[ourlang]

The database transaction files generated every day occupy 5G and require manual processing each time. Do you have any other configurations? Thank you

[pacmano1]

That is a SQL server exercise, not a Mirth question. Set recovery mode to simple. I assume you have a SQL job to automate all the SQL server stuff like truncating the log on backup. If not, you should use the maintenance solution at https://ola.hallengren.com/. Best stuff ever.

[pacmano1]

I suspect your channel may also be poorly designed and not use attachment handlers.

[ourlang]

what is attachment handlers

[ourlang]

Is this configuration correct？

[pacmano1]

Please go read up on attachments if you are processing large files. https://forums.mirthproject.io/articles/175046-using-attachments.

Those settings are fine - but you also need to check that pruning is enabled under settings.

[pacmano1]

Please stop posting to issues unless there is a known bug or you have a feature request. I am converting this to a discussion.