Redgate Test Data Manager
Published 16 October 2023
Get a masked and subsetted copy of your database, ready for dev and test.
Important – In all cases, we recommend you use a separate, non-essential environment when testing Anonymize and Subset. We cannot accept responsibility for any issues resulting from setting up Anonymize and Subset. Any activities carried out on production or otherwise important systems are not advised and at your own risk.
Before you start
- A database (SQL Server, PostgreSQL, MySQL or Oracle)
- Test Environment: Use a dedicated test environment to keep live data safe
- System Requirements: Make sure your system meets our minimum requirements in the installation guides here for a smooth setup. And check out some suggested set up tips in our architecture diagrams
- Check Foreign Key Relationships: Subset requires Foreign Key relationships. We've created some scripts to help you identify FK links across your database.
- A connection string with the correct level of access to the database see here for Anonymize and here for Subset
- A license, start a free trial during the sign in and authentication step
Using an AI coding tool?
If you're using Claude Code, Cursor, Copilot, or any AI coding tool, paste the prompt below into your tool.
It will walk you through activating your licence, installing the CLI, classifying your schema, and masking your data.
- Anonymize a database (works for SQL Server, PostgreSQL, MySQL/MariaDB, Oracle)
- Create a subset (works for SQL Server, PostgreSQL, MySQL/MariaDB, Oracle)
Prefer a GUI?
- Download the GUI installer
- Install the GUI
- Configure the TDM GUI
- Create a database model
- Create an anonymization treatment
- Run the anonymization treatment
What next
- Run this in CI/CD → /command-line-interface-cli
- Go deeper with the CLI → /command-line-interface-cli/anonymization/anonymization-worked-example
- Rolling out TDM across your team → /getting-started/implementation-checklist
- Something went wrong → /troubleshooting
