ApexSQL Log doesn’t recover non-index column updates in a clustered table

Applies to
ApexSQL Log

When reconstructing updates using ApexSQL Log in a table with a clustered index on multiple columns, update reconstruction fails for the non-index columns.

The error is encountered in a specific situation. The table where records were updated has a clustered index created on multiple columns. The update affects only the columns on which the clustered index is not defined.

For example, the table has the following columns: AddressID, AddressLine1, AddressLine2, City, and StateProvinceID. The clustered index is created on the first three columns; the City column has been updated.

The update for this column cannot be reconstructed, the Option details tab shows only the columns used for the clustered index.

ApexSQL is currently working to fix this issue permanently.