When should you consider it?
Best suited to application teams that need policy-driven, relationally intact subsets and clones for testing, QA, training or lower-cost non-production environments.
Editorial fit assessment based on the sources below.What are the limits?
Distinguish TDM subsetting and cloning from Solix Data Masking. Confirm synthetic-generation support and supported application/database versions for the exact product.
Which capabilities are documented?
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 reviewed datasheet describes database subsetting and cloning but does not specify a current deployment topology or edition matrix; treat deployment details as unknown pending vendor confirmation.
The reviewed datasheet gives a sales contact, not public license tiers or pricing; request a quote from Solix.
Sources and scope
- Solix Test Data Management Product Datasheet
Current vendor TDM positioning as secure subsetting/cloning; reusable configuration policies and referential integrity.
Source checked: 2026-10-01 - Solix Data Masking
Solix separately markets data masking for dev/test and data workflows; supports product-boundary distinction.
Source checked: 2026-10-01 - Optimize Test Data Management With Solix
Solix page presents masking capabilities in a TDM setting, but includes an author disclaimer; not treated as primary proof for synthetic generation.
Source checked: 2026-10-01
What should you verify in a proof of concept?
- Your database version, schema constraints and target formats.
- The exact product, edition, deployment and license entitlements.
- Your business assertions and the meaning of repeatability for your output.
- A failed run, cleanup and a repeat run on controlled inputs.