Does this generate valid SQL I can run directly?

Yes. The output is standard INSERT syntax with properly escaped string literals — single quotes are doubled per the SQL standard. Identifiers are quoted with backticks for MySQL and double quotes for PostgreSQL and SQLite, so you can paste the result straight into a console or seed file.

What is the difference between single multi-row and one-per-row INSERTs?

A single multi-row INSERT lists every row under one INSERT INTO statement, which is faster to execute and more compact. One-per-row produces a separate INSERT per record, which is easier to comment out, reorder, or run individually. Toggle whichever fits your workflow.

Is my schema or data sent to a server?

No. The entire generator runs locally in your browser using JavaScript. Nothing about your table, columns, or generated rows leaves your device, so it is safe to use with internal schema names.

How do I get the same rows every time?

The generator uses a seeded pseudo-random source, so the same configuration produces the same rows on each render. Press Reshuffle data to advance the seed and get a fresh batch of values.

What column types are supported?

You can choose auto-incrementing ids, integers, decimals, booleans, UUID v4, text, first or last or full names, emails, cities, ISO country codes, dates and datetimes. Each type emits values formatted correctly for that SQL column.

Mock SQL Rows Generator

Generate seed data without hand-typing rows

The Mock SQL Rows Generator turns a quick table definition into a block of ready-to-run INSERT statements filled with realistic fake data. Instead of writing seed rows by hand, you declare each column and its type, pick a SQL dialect, and copy out as many rows as you need to populate a development or staging database.

How it works

You build a lightweight schema in the browser: a table name plus a list of columns, each with a chosen type. For every requested row the tool walks your columns and emits an appropriate value — an incrementing integer for an auto id, an RFC 4122 version-4 string for a uuid, a name drawn from a curated pool for full name, and so on. String values are wrapped in single quotes with any internal quote doubled (O'Brien becomes 'O''Brien'), which is the SQL-standard way to escape literals and keeps the output safe to run.

Identifier quoting follows the dialect you select: MySQL uses backticks around table and column names, while PostgreSQL and SQLite use double quotes. You can emit one compact multi-row INSERT or a separate statement per row. A seeded random source keeps results reproducible until you press Reshuffle.

Tips and notes

Put your primary key first as an auto id column so the rows number cleanly from 1.
Use the datetime type for created_at and updated_at columns — values come out in YYYY-MM-DD HH:MM:SS form that all three dialects accept.
For large seeds, the single multi-row mode is faster to execute than hundreds of individual statements.
Everything runs locally, so you can safely paste real internal table and column names without leaking anything.