Data Quality Retention Settings
Retention settings control how long Ataccama ONE keeps DQ evaluation and profiling results. You can set limits to comply with data protection regulations, reduce storage usage, or control whether sensitive data like invalid samples is collected at all.
Available settings
Collect invalid samples
Enable or disable collection of invalid record samples across all DQ monitors. This setting is enabled by default.
-
When enabled, individual monitors can be configured to collect samples of invalid records during DQ evaluation.
-
When disabled, sample collection is unavailable in all monitors.
Delete history of data quality evaluations
Set how long to retain DQ evaluation and profiling results.
After the specified period, the results are permanently deleted and cannot be recovered.
| This includes invalid record samples and exported invalid records (for non-pushdown processing). If these contain sensitive data, you can set a shorter retention period using Delete invalid samples and exported records—whichever period is shorter applies. |
Delete invalid samples and exported records
Set a shorter retention period for invalid record samples and exported invalid records.
These records contain actual field values that failed validation—often the most sensitive data from your source systems. Use this setting if you need to delete them sooner than other DQ results.
When both this setting and Delete history of data quality evaluations are configured, the shorter period applies.
After the retention period, data is permanently deleted and cannot be recovered.
| For pushdown processing, exported records remain in your source database and you manage retention there. See export-invalid-records.adoc#storage-and-retention for details. |
Configure retention settings
Configuring retention settings requires the ONE Administrator governance role.
To configure retention settings:
-
Navigate to Global settings > Data retention settings > Data quality and profiling.
-
Enable or disable collection of invalid samples and set retention periods.
-
Publish the changes.
After publishing, retention policies are applied on every full hour or when a DQ evaluation starts.
Best practices for setting retention periods
When setting retention periods, balance compliance, investigation, and storage needs.
Compliance first: Check your data protection regulations before setting retention periods. Some industries require specific retention periods or prohibit storing certain sensitive data.
Investigation workflows: Set retention periods long enough to investigate and resolve typical data quality issues. Consider your average issue resolution timeframe.
Trend analysis: Longer retention enables better trend analysis and helps identify patterns over time. It also improves anomaly detection accuracy.
Storage costs: Balance retention needs with storage budget. Longer retention periods increase storage usage.
Was this page useful?