Ambiguous subset specifier
Published 06 March 2025
Starting tables and a desired size are both defined in your configuration. These two subsetting approaches cannot be used together.
Why this happens
The subsetter supports two different subsetting strategies that are mutually exclusive:
Starting tables approach: Follows relationships from specific tables with optional filters
Desired size approach: Automatically selects data to reach an approximate target size
How to fix
Choose one subsetting strategy and remove the other from your options file:
Option 1: Keep starting tables (remove desired size)
{ "startingTables": [ { "table": { "schema": "dbo", "name": "Users" }, "filterClause": "OrgId = 1" } ] // Remove "desiredSize" property }
Option 2: Keep desired size (remove starting tables)
{ "desiredSize": "25%" // Remove "startingTables" array }
When to use each approach
Starting tables: When you need specific data relationships (e.g., all data for Organization ID 1)
Desired size: When you need a general sample of your database at a specific size