Skip to main content

IAM Db size is (too) big. But Why?!

  • November 4, 2020
  • 1 reply
  • 91 views
Blommetje
Forum|alt.badge.img+13

Hi all,

Currently my IAM Db is quite large. The main culprit is the table “get gui cache”, which takes up far over 1gb. 

I do not know/understand why this is, and this is driving the costs for backups through the roof… 

So, just for conversation.. How big is yours? :wink:

I created a ticket within TCP, and I can clear it manually, but that does not feel like a great solution. Other than that, they send me over here and discuss it. So, let’s! 

Any thoughts on this? 

Kind regards, 

Alex 

Did this topic help you find an answer to your question?
This topic has been closed for comments

Mark Jongeling
Administrator
Forum|alt.badge.img+23

I do think it has to do with caching indeed but mostly with logging actions. The more users you have with Complete User preferences, the more log actions will be saved. This over time can get huge. The project I'm working on, in the development IAM, we all have Complete user preferences.

Small snippet of the Disk use per table:

I do have to note, it is a huge project with over 1200 tables+views and up to 30 active IAM applications. 

*The project has this IAM database On premise (for now)

"Wake me up before you low-code"
Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings