1

Our production database contains confidential information, that we dont want our developers to see.

Is there a normal workflow to get around this confidentially issue, without majorly impacting on the developers workflows / ability to trouble shoot.

We are using mysql 5.x

sam
  • 9,486
  • 36
  • 109
  • 160
  • 1
    Sure, create a dev database that has junk data in it. – mituw16 May 14 '14 at 14:16
  • 2
    Usually that is handled either via contract as in Non-Disclosure agreement or you only provide them dummy data. – VikingBlooded May 14 '14 at 14:16
  • We had this sort of problem working for a big insurance company. We had developers that were to verify bug reports from production... these were under NDA (most were employees of the insurance company) and would actually have access to production data. Other developers working on development and test environments would have dummy data. There was a system test environment that had a copy of all the production data pumped in during the night... but sensible information would be mocked by the copy procedure (it had a parametric list of tables/fields that had to be cleansed). – Frazz May 14 '14 at 14:23
  • 1
    you could create a `VIEW` [dev.mysql.com](http://dev.mysql.com/doc/refman/5.1/de/create-view.html) for each table where you randomize `rand()` every named content but still keep keys – JaMaBing May 14 '14 at 14:23

0 Answers0