When the DBUPDATES option is set to P on FDM (Fast Data Masker), FDM cannot create Pre/Poststep Scripts. FDM gives an error "Invalid object name 'SYSFOREIGNKEYS'."
It appears MSSQL version 2014 changed the reference from sys.foreignkeys to sys.foreign_keys. Does FDM need to be updated to account for this?
To check your instance, modify the following to work with your system:
SELECT DISTINCT (CASE WHEN OBJECTPROPERTY(CONSTID, 'CNSTISDISABLED') = 0 THEN 'ENABLED'
ELSE 'DISABLED' END) AS [STATUS], OBJECT_NAME(CONSTID) AS CONSTRAINT_NAME,
OBJECT_NAME(FKEYID) AS FK_TABLE, OBJECT_NAME(RKEYID) AS PK_TABLE, CONSTID FROM SYSFOREIGNKEYS WHERE OBJECT_NAME(RKEYID) = 'YOURTABLENAME'
A patch has been created to resolve this issue - FastDataMasker-220.127.116.11.zip. If you need this patch, please contact CA Support by opening a case. If you do not know how to open a case, please review this video and request this version or later. If you have a GA version after Sept 19, 2017, please verify with CA Support that this fix made it into the GA release.
You can download the latest version of TDM by following the directions in this document: https://support.ca.com/us/knowledge-base-articles.TEC1903942.html.
To contact support, go to https://www.ca.com/us/services-support/ca-support/contact-support.html.