We're getting an issue where certain tables are masked inconsistently if a disabled unique index includes the masked column. When this happens, only a portion of the lines are masked. Anything not masked is ignored by FDM (the de_ident_ind column remains null)
Masking "maskVal" with a SEQCHAR (although any function can be used) in the following table will only mask half the lines and ignore the other half.
Normally, we'd expect FDM to only use enabled indexes (in this case the primary key) for its SELECT and UPDATE statements.
This issue has been reproduced on SQL Server 2012, 2016 and 2019
Release : 4.10
This is resolved in FatsDataMasker-4.10.83.0
All primary & unique key columns are used for updating the database rows, although only primary key columns are sufficient.