testdatatools
Enterprise TDM

Informatica TDM

Informatica's documented TDM product is a web-based interface for data discovery, subsetting, masking and data generation. The 10.5.x documentation describes workflows and generation rules; distinguish this release line from separately marketed cloud services.

Sources reviewed

When should you consider it?

Best suited to Informatica environments that need governed discovery, persistent masking, relational subsetting and rule-based test-data generation.

Editorial fit assessment based on the sources below.

What are the limits?

The cited documentation covers the 10.5.x product line. Confirm supported databases, installation effort and commercial terms for the required release.

Which capabilities are documented?

Synthetic generationRules ยท TDM 10.5.x
De-identification / maskingTDM 10.5.x
Subsetting / subset planningTDM 10.5.x
Data virtualizationNot verified
Seeded replay, scopedNot verified

Documented means a cited vendor source describes this scoped capability. Not verified means the reviewed evidence cannot establish it. Neither is a hands-on test result.

How is it deployed and licensed?

The 10.5.8 documentation describes Test Data Manager as a web-based UI. Confirm the supported server topology and hosting options for your release.

No public price was found in reviewed Informatica material; confirm current availability, support lifecycle and commercial terms with Informatica.

Sources and scope

  1. Test Data Manager Overview - Informatica TDM 10.5.8

    Official documentation search result describes web UI and data discovery, subset, masking and generation operations.

    Source checked: 2026-10-01
  2. Define Data Masking and Data Subset Operations

    Official 10.5.8 documentation covers definition of masking and subset operations.

    Source checked: 2026-10-01
  3. Creating an Advanced Generation Rule

    Official documentation for rule-based single/multi-column data generation and foreign-key grouping.

    Source checked: 2026-10-01

What should you verify in a proof of concept?

  1. Your database version, schema constraints and target formats.
  2. The exact product, edition, deployment and license entitlements.
  3. Your business assertions and the meaning of repeatability for your output.
  4. A failed run, cleanup and a repeat run on controlled inputs.
Define your requirements and proof of concept