Please share any images or screenshots, if relevant.
[Please insert images here, otherwise delete this section]
Please share any other relevant files that may be required (for example, logs).
Below are two of the many options available in an account aggregation task. Enable Delta Aggregation - Enable the connector to aggregate only those accounts that have changed since the last aggregation. This requires support by the connector. Disable Optimization of unchanged account - Use this option to force all accounts to be aggregated, even if unchanged since the last aggregation.
Share all details about your problem, including any error messages you may have received.
What is the difference between âEnable Delta Aggregationâ and âDisable Optimization of unchanged accountâ options in the in Aggregation task?
They both sound similar. If we enable both, then what is the result of the aggregation? As in only changed accounts will be aggregated or force all accounts to be aggregated?
we can say that Delta work on target side, Optimization on Sailpoint side.
With the Delta, IIQ request only changed object to the target system.
With Optimization, IIQ recive all the data but work only on changed object.
For example, if you 50k account on AD but only 5k are changed, with delta IIQ receives the only 5k; with Optimization, IIQ receives 50k but will work on 5k.
You can use both for improve the performace.
PS Delta is not avaible for all target system or you must work on target system before the activation(ex. JDBC)
Before diving into the options, itâs helpful to understand what aggregation means in SailPoint:
Aggregation is the process by which SailPoint connects to external systems (like HR systems, directories, or applications) to collect and import user account information into its identity warehouse.
This process keeps SailPoint updated about who has access to what across all connected systems.
1. Enable Delta Aggregation
What It Means in SailPoint:
Delta Aggregation tells SailPoint to only fetch and update accounts that have changed since the last time it checked.
When you enable this option, the connector (the bridge between SailPoint and external systems) will look for accounts that are new, modified, or deleted and only bring in those changes.
Why Itâs Useful:
Efficiency: Saves time and system resources because SailPoint doesnât have to process every single account every time.
Performance: Reduces the load on both SailPoint and the connected system, making the aggregation process faster.
Timeliness: Quickly reflects recent changes in user accounts within SailPoint.
Requirements:
The connector must support delta aggregation. Not all connectors have this capability, so you need to ensure that the one youâre using does.
Analogy:
Itâs like checking for new mail in your inbox. Instead of reading all your old emails every time, you only look at the new ones that have arrived since you last checked.
Example in SailPoint:
Suppose you have an HR system connected to SailPoint. When a new employee is hired or an existing employee updates their information, enabling delta aggregation means SailPoint will import just those changes, updating its records accordingly.
2. Disable Optimization of Unchanged Accounts
What It Means in SailPoint:
By default, SailPoint might skip over accounts that havenât changed to make aggregations fasterâthis is called optimization.
Disabling this optimization means youâre telling SailPoint to process every account, regardless of whether it has changed since the last aggregation.
Why You Might Use This:
Data Accuracy: Ensures that SailPointâs records are fully synchronized with the connected system.
Detecting Missed Changes: Captures any updates that might have been overlooked or not properly flagged in previous aggregations.
Compliance and Auditing: Important when you need to verify that all account data is up-to-date for security audits or compliance requirements.
Analogy:
Similar to doing a full inventory check in a storeâyou count every item to make sure your records match whatâs actually on the shelves, even if you believe nothing has changed.
Example in SailPoint:
After a system upgrade or data correction in your source system, you might disable optimization so SailPoint re-imports all account data, ensuring that no discrepancies exist between the systems.
Putting It All Together in SailPoint
When to Use Each Option:
Enable Delta Aggregation:
Use When: You want SailPoint to quickly update with only the latest changes.
Benefit: Faster aggregations with reduced system load.
Disable Optimization of Unchanged Accounts:
Use When: You need a complete refresh of all account data in SailPoint.
Benefit: Ensures all account information is current and accurate.
Considerations:
Performance Impact:
Delta Aggregation improves performance by processing fewer accounts.
Disabling Optimization may slow down aggregation because all accounts are processed.
Data Integrity:
Delta Aggregation relies on the connector accurately identifying changed accounts.
Disabling Optimization guarantees that all accounts are reviewed and updated if necessary.
Scenarios in SailPoint
Scenario 1: Routine Daily Operations
Situation: Your organization has daily changes like new hires or role updates.
Action: Enable delta aggregation.
Result: SailPoint quickly imports only the changes, keeping data current without unnecessary processing.
Scenario 2: Post-Maintenance or Data Correction
Situation: Youâve performed significant updates to user data or corrected issues in the source system.
Action: Disable optimization of unchanged accounts.
Result: SailPoint reprocesses all accounts to ensure its data matches the source system exactly.
Scenario 3: Compliance Audit
Situation: An upcoming audit requires absolute certainty that all user access information is accurate.
Action: Disable optimization to force a full aggregation.
Result: Provides assurance that SailPointâs data is fully up-to-date, supporting compliance efforts.
Key Takeaways for SailPoint Users
Enable Delta Aggregation:
Ideal For: Regular updates where only a subset of accounts change.
Benefits: Improves performance, reduces load, and keeps data fresh.
Disable Optimization of Unchanged Accounts:
Ideal For: Situations requiring full synchronization of all account data.
Benefits: Ensures data accuracy across all accounts, which is crucial for compliance and auditing.
Connector Compatibility:
Remember that delta aggregation requires connector support. Check your connectorâs capabilities before enabling this option.
Practical Tips
Before Enabling Delta Aggregation:
Verify that the connector supports it.
Ensure that the connected system properly tracks changes to accounts.
Before Disabling Optimization:
Be prepared for longer aggregation times.
Plan to run the aggregation during off-peak hours to minimize impact on system performance.
Conclusion
In SailPoint, managing how you aggregate account data is crucial for balancing performance and data accuracy:
Use Delta Aggregation when you need efficient, incremental updates.
Disable Optimization when you need to ensure complete data synchronization, such as after major changes or for compliance reasons.