IAM database growing alot in physical size how to reduce

Shrinking a database causes severe index fragmentation and is something that should be avoided unless absolutely necessary, after a large one-time only delete action. So a shrink is best performed outside business hours with a index rebuild right after.

Also make sure to leave some space left since a database always grows, leaving 20% empty space is a good rule of thumb. 

Hello ​@Anne Vries,

I think you already found the relevant documentation for the retention of the logs. For good measure I will also include them here:

• Web connection log is part of Environment monitoring on an Application level: https://docs.thinkwisesoftware.com/docs/iam/system_flows#application-log-retention
• Process flow schedule log: https://docs.thinkwisesoftware.com/docs/iam/system_flows#schedule-log-settings

If you decreased the retention time for these logs, they should be cleaned up automatically using a system flow. If you want to delete these logs before that, you indeed would need to do that using your own SQL queries.

Hope that helps!

Yes

I have reduced them to their minimal values. Is it possible to reduce them even further or even turn it off for specific applications?

Hello ​@Anne Vries,

It is not possible to decrease these log retention periods any further. I would also not expect the logs to grow to an excessive size within that period.

If you still  would prefer to decrease (or turn off) the retention periods, you could make an Idea on the community for this.