January 14, 2014 at 8:38 am
Hi everybody
We have a requirement to de-sensitize some of the data in our tables after we do a restore to our test\dev environment. We need to replace the data with some kind of meaningful test data that our software tester can run tests against.
Can anybody point me to any scripts\methodologies that may handle this type of task as it is a first for me.
January 14, 2014 at 9:03 am
Basically I think you need custom scripts that run as part of your restore process to clean up the data before people use it. Essentially follow this:
- restore db
- set restricted user
- run obfuscation script
- if works, set all users
A few links:
https://www.simple-talk.com/sql/database-administration/obfuscating-your-sql-server-data/
http://www.brentozar.com/archive/2011/09/how-do-you-mask-data/
http://www.sqlservercentral.com/Forums/Topic461773-61-1.aspx
http://documentation.red-gate.com/display/SDG3/Using+SQL+Data+Refresh
Disclosure: I work for Red Gate Software.
January 14, 2014 at 10:59 am
PearlJammer1 (1/14/2014)
Hi everybodyWe have a requirement to de-sensitize some of the data in our tables after we do a restore to our test\dev environment. We need to replace the data with some kind of meaningful test data that our software tester can run tests against.
Can anybody point me to any scripts\methodologies that may handle this type of task as it is a first for me.
If it's a 3rd party db have you tried contacting the vendor?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 14, 2014 at 11:00 am
Here is one from a colleague that I haven't used before, so please test first:
http://www.robusthaven.com/products/production-management/SQL-Data-Obfuscator
One more for jumbledb http://www.orbiumsoftware.com
January 15, 2014 at 4:20 am
Ok thanks for the replies everyone - looks like a complicated process to implement. I'm going to have to give this some serious thought.
:-):-)
January 15, 2014 at 4:57 am
PearlJammer1 (1/15/2014)
looks like a complicated process to implement. I'm going to have to give this some serious thought.:-):-)
What?
Identitfy the Live tables that require obfuscating (there's likely only a few). Build yourself a set of generic tables with meaningless names, addresses, etc and use these to obfuscate the real data 😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 15, 2014 at 5:36 am
Perry Whittle (1/15/2014)
PearlJammer1 (1/15/2014)
looks like a complicated process to implement. I'm going to have to give this some serious thought.:-):-)
What?
Identitfy the Live tables that require obfuscating (there's likely only a few). Build yourself a set of generic tables with meaningless names, addresses, etc and use these to obfuscate the real data 😉
exactly what i do; i have a bunch of tables like Ansi color names, animal names, actor names that i use for updating existing data with meaningful but clearly obfuscated data elements.
Lowell
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply