Enterworks - ETT 123 - How to Detect and Resolve Snapshot Discrepancies Without Rebuilding the Entire Table

Enterworks - ETT 123 - How to Detect and Resolve Snapshot Discrepancies Without Rebuilding the Entire Table

Data Model, Snapshot

rate limit

Code not recognized.

About this course

The EnterWorks snapshot tables provide a relational view of the repository data to facilitate link relationships between repositories, Bulk Callout validation rules, EPX workflow access to repository data, improved performance in the repository list view, and SQL access from external applications. Every time the attribute data is updated in a repository record, the corresponding snapshot table record is supposed to be updated to reflect that change. There are some circumstances in which the snapshot table does not get updated. One example would be if a promotion job is aborted mid-processing, the Production repository data may have been updated, but the corresponding snapshot table records (which in the case of Promotions are handled as a subsequent step) was not performed. If this happens, operations that access the snapshot table (which may include the repository list view if all attributes in the selected User Preference are in the snapshot table) will show data that is different from the current data stored in the repository.

There have been two ways to resolve the discrepancies between the repository data and the corresponding snapshot records:

1. Edit the record and save a change - this updates the corresponding snapshot table record.

2. Rebuild the entire snapshot table - this removes all snapshot data and re-loads it from the repository.

The challenge with resolving discrepancies by editing and saving records is that it may not be obvious which records need to be edited and large numbers of records would be tedious to manually edit each one. The challenge with rebuilding the snapshot is that during the build process, anything that relies on the snapshot table data will be negatively affected. With larger repositories, the rebuild may take some time. A new tool in the form of a SQL Stored Procedure has been developed by Customer Support to report or correct discrepancies in a repository's snapshot table, eliminating the need to manually edit and save records or to rebuild the entire snapshot table. This session provides details on how to use the Stored Procedure to find and eliminate the snapshot table discrepancies.

Prerequisites - ETT 024

About this course

The EnterWorks snapshot tables provide a relational view of the repository data to facilitate link relationships between repositories, Bulk Callout validation rules, EPX workflow access to repository data, improved performance in the repository list view, and SQL access from external applications. Every time the attribute data is updated in a repository record, the corresponding snapshot table record is supposed to be updated to reflect that change. There are some circumstances in which the snapshot table does not get updated. One example would be if a promotion job is aborted mid-processing, the Production repository data may have been updated, but the corresponding snapshot table records (which in the case of Promotions are handled as a subsequent step) was not performed. If this happens, operations that access the snapshot table (which may include the repository list view if all attributes in the selected User Preference are in the snapshot table) will show data that is different from the current data stored in the repository.

There have been two ways to resolve the discrepancies between the repository data and the corresponding snapshot records:

1. Edit the record and save a change - this updates the corresponding snapshot table record.

2. Rebuild the entire snapshot table - this removes all snapshot data and re-loads it from the repository.

The challenge with resolving discrepancies by editing and saving records is that it may not be obvious which records need to be edited and large numbers of records would be tedious to manually edit each one. The challenge with rebuilding the snapshot is that during the build process, anything that relies on the snapshot table data will be negatively affected. With larger repositories, the rebuild may take some time. A new tool in the form of a SQL Stored Procedure has been developed by Customer Support to report or correct discrepancies in a repository's snapshot table, eliminating the need to manually edit and save records or to rebuild the entire snapshot table. This session provides details on how to use the Stored Procedure to find and eliminate the snapshot table discrepancies.

Prerequisites - ETT 024