Mockers
Last updated
Was this helpful?
English
Last updated
Was this helpful?
are used to generate entirely new, random values for a column. They are ideal when privacy is the top priority, and there’s no need to maintain a link to the original data values.
To fill columns that contain directly identifiable information (PII)
To populate empty columns
When format matters, but data relationships do not
Mockers are grouped by data type:
Numeric (and )
Follow the interactive guide below to apply a mocker.
Constraints on Key Columns: Mockers cannot be applied to primary key or foreign key columns.
Column-by-Column Operation: Mockers function on individual columns. At this point, they can't be used to preserve logical relationships across multiple columns.
Automatically Cutoff Values: The Syntho platform automatically cuts off generated mock text values based on the data type's supported length. For example, a mocker applied on an NVARCHAR(5) column, will cutoff all values beyond the first 5 characters of the text.
Automatically Clip Values: The Syntho platform automatically clips numerical values that exceed the maximum or minimum size, to the largest or smallest value supported by the data type, respectively.
No Link with Original Records: Mockers do not link back to the original data records, enhancing privacy but potentially reducing the usefulness of the data. If you want to retain the link with the original values, you can enable the feature.
Database Type Compatibility: The return type of a mocker indicates its compatibility with specific database data types. For example, a mocker with a text return type is compatible with database types like (N)VARCHAR or TEXT, but not with a database type NUMERIC (INTEGER). It is important to this into account when applying mockers on your columns to prevent your data generation job to fail.
Being aware of these limitations and considerations will help you effectively use mockers while understanding their constraints.