Featured post
mysql - what some ways to mask a mysqldump? -
anybody knows efficiency in masking(anonymization) of tables in mysqldump? have finished parser unfortunately doesn't work on big dumps (let dump of 1gb++) because increases dump time due parsing.
what did parse table columns first (which shouldn't take long) , parse whole insert string specific table.
i using ruby , use if possible.
i looked idea of exporting dump, dumping it, updating (masking) through internal ruby code exporting dump again. although haven't tried how long going take.
the current workflow be: dump server, uncompress, dump mysql
the new 1 dump server, uncompress, masked confidential data , dump mysql
the current workflow take @ 2 hours 1-2gb++ dump unfortunately spent 4hrs on new 1 still not finished on parsing/masking part.
i advised improvise code taking out variables , things consumes more memory since ruby gc said not on 1:1 ratio. believe optimized on ree(ruby enterprise edition) using ree now.
has done , maybe share thoughts? thanks.
you can specify tables don't want dump: http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html#option_mysqldump_ignore-table
- Get link
- X
- Other Apps
Comments
Post a Comment