About SQL to Excel
SQL to Excel is for the times you have a database dump but no database: a backup from a hosting panel, an export from phpMyAdmin, a .sql file a developer sent over. Upload it and the rows in its INSERT statements land in an Excel workbook, one sheet per table, so you can search, filter and check the data without setting anything up. To pass a table on to another system, Excel to CSV can then save each sheet as a CSV.
Column names come from the INSERT column list, or from the matching CREATE TABLE when the INSERT has none. Quoted text is unescaped, including doubled quotes and escaped line breaks, NULL becomes an empty cell, and numbers arrive as numbers. INSERT statements as written by mysqldump, phpMyAdmin, SQLite's .dump or pg_dump --inserts are read directly. pg_dump's default COPY format isn't, because it contains no INSERT statements.
How to use SQL to Excel
- 1Upload the .sql file
Choose or drop the dump. It can hold CREATE TABLE and other statements; only the INSERTs are turned into rows.
- 2Click SQL to Excel
Every INSERT is parsed on our server and its rows are grouped by table.
- 3Download the workbook
Each table gets its own sheet, named after the table, with a frozen header row.
Why use Cubfile for this
- One sheet per table
users, orders and products from the same dump end up side by side in one workbook.
- Real column names
Taken from the INSERT itself or from CREATE TABLE, with column_1, column_2 as a fallback.
- Values cleaned up
Quotes are unescaped, NULL is left blank and numbers are stored as numbers.
- No database needed
Read a dump on any computer without installing MySQL, PostgreSQL or a SQL client.