Overview

This checklist is designed to guide new users through the basic setup and deployment of our Redgate Test Data Manager, providing a straightforward roadmap for a successful Proof of Concept (PoC).

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

Please note – 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 against our advice and at your own risk.

Before You Start: What you need to know 

• Test Environment: Always use a test environment for your PoC. This keeps your live data safe.
• System Requirements: Make sure your system meets our minimum requirements here for a smooth setup. And check out some suggested set up tips in our architecture diagrams.
• Skills needed: You'll need some Linux skills and preferably some Kubernetes/Docker knowledge.
• Redgate University Courses: For videos and top tips from the experts, take a look at our Test Data Manager courses on Redgate University.

Installation / Download Overview

Clone Installation

• We'd recommend starting with the installation of Clone as this will provide your environment for delivering test data.
• See our guide on how to get set up.

Getting clone up and running

1. Start empty: Get yourself an empty container up and running
2. Add Sample Databases: Load databases, for example a sample database, or pre-prepared database, into your container for testing.
3. Use Anonymized Data: Incorporate anonymized data from a previous scrubbing project.
4. Scale Up: Increase capacity as needed.

Anonymize, Subsetting and Data Generation Command Line Installation

• Anonymize: For installation and initial setup of the Anonymize tool, refer to this link.
• Subsetting: Installation instructions for the Subsetting tool and requirements.
  • Subsetting requires both a source database, usually a rehydrated copy of production, and a target database. More detail below.
• Data Generation: See our guide for installing and starting with the Data Generation tool.

For some suggested workflows for Test Data Manager, and visual explanations of the subset and anonymize command lines take a look at our architecture pages.

Source database

• Primary Database for Changes: Use a development database to make and capture changes. Ensure you have full access (e.g., SQL Server = db_owner; Oracle = schema owner).
• Backup of Production Database: It's advisable to create a backup of your production database for testing purposes.

Target database

• For Subsetting: When using the command lines for subsetting, provision a target database that is empty and schema-only.
• Isolation for Initial PoC: Use an isolated database without linked servers or cross-database dependencies for simplicity. Do let us know if your real projects require these features.

Output: A backup file for clone