Version 8.4
2024-04-25T18:30:00Z
Hi SailPoint,
While upgrading i found there is no recommendation for size of database for Access History. This can be issue for any client because azure database size charge decent cost.
Also, if we have option for insert last 4 year data for inactive account then that will also save some size of database.
To begin with consider the same size database size as your Identity IQ database, or at-least 70% of the size of it. and exepct it to grow.
Okay, I will tell my POV only based on my understanding :).
Yes, correct, There are no specific recommendations or steps, because it’s super vary also need to know more about your organization’s requirements, compliance needs, and data usage patterns, I can offer some general guidelines that you can tailor to fit your specific situation:
Determine the required retention period for access history data based on regulatory compliance requirements, audit policies, and business needs. For example, some regulations may require data retention for specific years/months.
Estimate the growth rate of access history data over time based on historical data usage patterns and future business projections. This can help you plan for future database size requirements and budget accordingly.
Regularly monitor database size and implement strategies to stay within these thresholds, such as data purging or archiving.
It’s important to collaborate with stakeholders from IT, security, compliance, and business departments to plan this effectively.
How many CPU cores we needed for access history data base
Currently we have 12 core data base for
vCores - 12vCores
max storage - 725 gb
used - 270 gb