Comments
1 comment
-
Hey @... have you tried using a Sync Manager? You can use the same method mentioned here: Masking Primary and Foreign Keys - Advanced Operations with Data Masker for SQL Server - Redgate University (red-gate.com)
The values don't actually need to be PKs/FKs rather can be a distinct set of values across 2 tables with no PK/FK relationship between them
Add comment
Please sign in to leave a comment.
The masked SSN value should never be a real SSN.