We are planning to increase the number of Identity Extended Attributes in our SailPoint IdentityIQ production environment. Before proceeding with the required database changes, we wanted to check if anyone has encountered issues while making similar updates. Specifically, we are interested in understanding any potential risks, performance impacts, or challenges faced during or after the change. Additionally, we would appreciate any guidance on best practices or precautions that should be taken to ensure a smooth and safe implementation.
Thank you in advance for your insights and recommendations.
@Prash Please follow the shared above article to understand how to extend the columns. However you need to find a right balance when it comes to number of columns in a table. If you have more columns then you may see below issues:
Increased Logging Overhead → Every time you insert data, the database must write that transaction to a log file. Ex: A row with 10 columns might generate a 500-byte log entry. A row with 40 columns might generate a 1-2KB log entry.
Index Maintenance → Each index on a table must be updated synchronously during an insert.
Increase in insertion/query time → It takes slightly more time when you perform insertion/Select on a table with more columns. It will impact views as well if configured. You may not see the differences for lesser data, but where you have so many identities, having too many columns slows down the aggregation and refresh tasks.
Note: Found a fix?Help the community by marking the comment as solution. Feel free to react(,, etc.)with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.
,
, etc.)with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.