Efficiency up, failed releases down; compliant production data for your test and dev environments
summary
Claim: realistic, compliant copies of production cut failed releases and speed development by giving developers usable data without exposing secrets. Workflow shown: tag sensitive fields with Redgate Data Catalog, export a mapping file, run rules in Data Masker (static/substitution, linked columns, gender-aware passes), create one masked image and deliver many writable copies with SQL Clone. Handles very large estates (examples: 10–50+ TB, 34 TB restores, 64 TB image limit), demo completes end-to-end and the clones work for self‑service dev and testing.
AI-written summary · about
chapters (14)
- 0:00Compliant production data intro
- 3:19Why production data is risky
- 6:55Realistic test data role
- 9:05Identifying and cleaning data challenges
- 12:42Data management hurdles
- 18:27Tagging data for compliance
- 26:12Never use production data directly
- 27:14Generated vs masked data
- 30:06Large DBs in development
- 32:37DB sharing limits
- 35:44Risks of unmasked data
- 38:40Catalog and masking tools
- 40:46Demo: Masking and cloning DBs
- 47:14Summary and Q&A
related talks
47mEfficiency up, failed releases down; compliant production data for your test and dev environments
47mEfficiency up, failed releases down; compliant production data for your test and dev environments
48mDevOps Discovery: Navigating the Database Landscape
37mTransforming Test Data Delivery for Shift Left Automation (Closing Keynote)
48mDevOps Discovery: Navigating the Database Landscape
24mData Masking & Virtualization
46mTransform your development workflow with thin cloning
34mTest Data Management Principles
