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.
You need to go the location identityiq_home\WEB-INF\classes\sailpoint\object\ where identityiq_home is identityiq installation path and add the extended attributes to the LinkExtended.hbm.xml file.
And then connect to the console and run the command iiq extendedSchema , this command creates the database scripts named add_identityiq_extensions.mysql and run the generated script in database to add the extended attributes to the Link table in identityiq database.