Redgate Test Data Manager

Implementation checklist

Overview

This checklist guides new users through setting up and deploying Redgate Test Data Manager for a successful Proof of Concept (PoC).

Our product includes a user-friendly GUI along with powerful CLI tools including anonymize and subsetting.

Important – In all cases, we recommend you use a separate, non-essential environment for the Proof of Concept. We cannot accept responsibility for any issues resulting from setting up the Proof of Concept. Any activities carried out on production or otherwise important systems are not advised and at your own risk.

Before You Start: What you need to know 

  • Test Environment: Use a dedicated test environment to keep live data safe similar to the proof of concept environment below.
  • 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.
  • Redgate University Courses: For videos and top tips from the experts, take a look at our Test Data Manager courses on Redgate University.

Download Test Data Manager

Get the latest versions:

📥 GUI (Windows only)
Download the GUI installer | See installation guide

📥 Command line tools (Windows/Linux)
- Download Anonymize CLI | Installation guide
- Download Subsetting CLI | Installation guide

Example Proof of Concept environment

 

Installation Overview

GUI Installation

📥Download GUI installer (Windows only)

Complete GUI Installation Guide - Follow our step-by-step guide that covers:

  • Hardware and software requirements
  • Installation procedure with screenshots
  • Initial configuration and testing

Command Line Installation

📥Download command lines

For automation, scripting, and CI/CD integration

Getting Started

Using the GUI

The Test Data Manager GUI provides visual workflows for subsetting and anonymization.

💡 Tip for subsetting, you'll need to prepare source and target databases. See create an empty target database for guidance.

Step 1: Create a database model 🔴 Required

You'll need: Database connection details (non-production environment)

Step 2: Choose your treatment type (Requires a database model)

Choose based on your goal:

Step 3: Run your treatment

Using the Command Line

For automation and scripting workflows

Subsetting

Getting Started with the Subset CLI - Create your first subset

Anonymize

For a step by step guide to Anonymize, check out our Worked Example.

For more details and advanced configuration options, refer to the Anonymize command line reference.


Next Steps

✅ Complete your first PoC:

  1. Create a database model
  2. Create an anonymization treatment OR Create a subsetting treatment
  3. Run your treatment and review results

📚 Explore advanced features:

🎓Learn More:



Didn't find what you were looking for?