Multi-database subsetting: preserving referential integrity
Explore multi-table and multi-database subsetting, and how this impactful process fuels targeted test data generation while strengthening data security.

Host

Chiara Colombi

Speaker

Johnny Goodnow
With big data getting bigger by the minute, subsetting is fast becoming a crucial step in representative data synthesis. But it isn’t easy.
Many synthetic data tools don’t even offer subsetting capabilities.
Preserving referential integrity across hundreds (or thousands) of tables is a challenge. Today, we’re taking that challenge one step further.
Staff Software Engineer Johnny Goodnow will shine a light on multi-database subsetting and how this impactful process fuels targeted test data generation while strengthening data security.
In this webinar, you’ll learn:
- Subsetting 101: what it’s been, what it is, and what it’s becoming
- Tonic’s approach: how we’re pioneering multi-database subsetting with multi-table seed data, to shrink entire data ecosystems down to a manageable, useful size
- Use Cases: from minimizing data exposure in developer and QA environments to maximizing data utility in targeted debugging
- Subsetting in action: a sneak peak into our newest subsetting features