Generate Sample Data
Generate test INSERT statements for one physical ERD Table and review them in inline SQL cards.
Target and prerequisites
Use one physical Table that exists in the real database.
- Select a regular Table connected to a real Connection from the ERD.
- Views, system Tables, Tables marked for deletion, and unapplied virtual Tables are excluded.
- Even with multiple Tables selected, only the right-clicked Table is targeted.
- The default is 20 rows; enter an integer of 1 or greater.
How to use
Start from the ERD Table context menu.
Check the target
Verify it is a physical Table and the INSERT auto-apply policy is intentional.
Choose AI: Generate Sample Data
Right-click the Table and choose the Sample Data action.
Enter the row count
Review the locked target and enter the default 20 or another positive integer.
Send and review INSERT
Review generated INSERT statements and results in SQL cards.

Request context
The target Connection, Database, and Schema are added to the current request automatically and locked.
- The complete target Table route appears in the attachment.
- The target context cannot be removed or changed to another route for this request.
- The current Chat is reused instead of switching to a new conversation.
- Other contexts can be added as supporting scope when needed.
Real-value lookup and protection
The AI can inspect metadata and limited actual values to produce constraint-compatible INSERT statements.
- It checks foreign keys, primary keys, unique constraints, defaults, and generated columns.
- It may query up to 10 actual rows for FK references and explicit PK or UNIQUE duplicate candidates.
- Actual-row lookups require Tool approval or an available persistent approval.
- Each lookup is limited to 30 seconds and excludes LOB and binary values.
Note: In account projects, when Always Mask Sensitive Data is on for the target Connection, sensitive values in lookup results are masked before being sent to the AI Provider.
Review and run INSERT
Generated INSERT statements appear as one inline SQL card per statement.
- Review columns, values, row count, and target Table.
- Run or copy from the SQL card, or open an editable regular SQL Editor copy.
- Database constraints, triggers, defaults, and generated columns are authoritative.

Caution: When data-change auto-apply is on for the target Connection, INSERT can run automatically.
Troubleshooting
If the menu is missing or Send is unavailable, check the following.
- Verify the target is a physical Table, not a View, system Table, or Table marked for deletion.
- Apply a virtual Table to the real database before starting again.
- Verify the row count is an integer of 1 or greater and the current project source has an active Provider Key.