If you use Horizon with any products using a SQL database (such as Loyalty), then change tracking must be enabled in your Microsoft SQL source databases to ensure that Horizon producers function correctly. Horizon uses change tracking to know what data has been changed, and what needs to be sent.
Horizon automatically turns on database change tracking when Horizon producers are installed.
Important: Turning off or changing change tracking settings can cause outages or disruptions in service.
These are the properties your SQL database needs to use change tracking:
| Option | Values | Description |
|---|---|---|
| Change Tracking |
True False |
This must be set to True. |
| Retention Period | Any number | The minimum period for keeping change tracking information. We recommend 30 days. |
| Retention Period Units |
Days Hours Minutes |
Specifies the units for Retention Period. |
| Auto Cleanup |
True False |
Determines whether change tracking data is automatically removed after the retention period. If you use manual change tracking cleanup, this will be set to False. |
Please check with your database administrator before making any changes to your database.
Example query to check if change tracking is turned on:
SELECT '[' + s.name + '].[' + t.name + ']' AS Table_name, data_retention_period, data_retention_period_unit_desc
FROM sys.change_tracking_tables tr
INNER JOIN sys.tables t on t.object_id = tr.object_id
INNER JOIN sys.schemas s on s.schema_id = t.schema_id
See also:
Comments
0 comments
Please sign in to leave a comment.