Data Masking Pack

From: Kenneth Naim <>
Date: Mon, 26 Oct 2009 14:12:36 -0400
Message-ID: <024101ca5667$e75ea440$b61becc0$_at_com>

My colleague implemented data masking of credit cards, ssn's and bank accounts and ran into some errors, so I was asked to review the code generated by the pack. It seems a lot more complicated than it needs to be. I see constraints/triggers/tables being dropped, renamed and recreated, procedures being created and later dropped for every table being masked, hundreds of lines of null being concatenated together etc. Is this the way this pack should work? Does this logic make any sense to any one? How is this better that a simple procedure that disables constraints and triggers, and generates a random value for the column and then perform a mass update.  



Received on Mon Oct 26 2009 - 13:12:36 CDT

Original text of this message