EnterWorks - ETT 131 - How to Re-Sequence the Item History Records Using SQL

EnterWorks generates history records any time a repository record is created, updated or deleted, and each record has an auto-sequenced ID to uniquely identify each record.  In versions prior to 10.5.3 and 10.6.1, a code issue causes problems when the IDs exceed the 32-bit maximum of 2,147,483,647.  Known impacts include:

• viewing the history for a record may not show the history records and differences in them accurately
• details of attribute changes made to a record may not be passed to the registered event handler, such as Change Notification, which impacts behavior relying on changes

The underlying issue has been addressed and will be included in new product releases after versions 10.5.2 and 10.6.  For earlier versions, if the 32-bit threshold is approaching or has been exceeded, a SQL-based process has been devised to re-sequence the IDs so new history records will be well below the 32-bit threshold.  This immediately resolves the issues relating to exceeding the threshold and lengthens the time before upgrading is necessary.  This session covers the details of the item history table and the process for re-sequencing the table's IDs.

Prerequisites - ETT 077