What SQL does it parse?

INSERT statements, specifically. CREATE TABLE and other DDL are ignored. The tool pulls row values out of INSERTs and formats as CSV.

Does it handle multiple tables?

Yes — but output is per-table. Each INSERT INTO table_name creates a separate CSV.

SQL's quote escaping ('it''s') is handled. The CSV output uses RFC 4180 double-quote escaping. Different rules, handled correctly.

For quick data extraction. For real migration use SQL dumps + language-specific importers. This is a debugging/inspection tool.

Convert SQL INSERT statements to CSV format. Part of the DevTools Surf developer suite. Browse more tools in the Data / SQL collection.

RFC 4180 formally standardized the CSV format in 2005, over 30 years after it was first used in practice.
The term 'fixture' in software testing originates from manufacturing, where a fixture holds a workpiece in a known position.
SQL INSERT parsing must handle escaped quotes, NULL literals, and multi-line values, making it deceptively complex.

What SQL does it parse?: INSERT statements, specifically. CREATE TABLE and other DDL are ignored. The tool pulls row values out of INSERTs and formats as CSV.
Does it handle multiple tables?: Yes — but output is per-table. Each INSERT INTO table_name creates a separate CSV.
What about escape sequences?: SQL's quote escaping ('it''s') is handled. The CSV output uses RFC 4180 double-quote escaping. Different rules, handled correctly.
Is this for database migration?: For quick data extraction. For real migration use SQL dumps + language-specific importers. This is a debugging/inspection tool.

Convert SQL INSERT statements to CSV format. Part of the DevTools Surf developer suite. Browse more tools in the Data / SQL collection.

RFC 4180 formally standardized the CSV format in 2005, over 30 years after it was first used in practice.
The term 'fixture' in software testing originates from manufacturing, where a fixture holds a workpiece in a known position.
SQL INSERT parsing must handle escaped quotes, NULL literals, and multi-line values, making it deceptively complex.

What SQL does it parse?: INSERT statements, specifically. CREATE TABLE and other DDL are ignored. The tool pulls row values out of INSERTs and formats as CSV.
Does it handle multiple tables?: Yes — but output is per-table. Each INSERT INTO table_name creates a separate CSV.
What about escape sequences?: SQL's quote escaping ('it''s') is handled. The CSV output uses RFC 4180 double-quote escaping. Different rules, handled correctly.
Is this for database migration?: For quick data extraction. For real migration use SQL dumps + language-specific importers. This is a debugging/inspection tool.