Merge SQLITE files

Join SQLITE files into one, end to end, in the order you add them.

Converted in an isolated sandbox on our serversDeleted after 24 hours

Drop SQLITE files on the dialor turn it to pick what to do

One database from many SQLite files.Add two or more files and get one SQLite database with every table.

  1. What you get

    One SQLite database that holds every table of every file you add. The files are joined end to end, in the order you add them.

    Tables with the same name are stacked into one table. Their rows follow the order of the files.

  2. How columns are matched

    Columns are matched by name. The first file's columns come first. A column that only a later file has is added at the end of the table.

    Where a table has no column for a cell, the cell stays NULL.

    Columns take DuckDB's types, such as BIGINT, DOUBLE and VARCHAR. If a table has values that do not match their column types, that table is kept as text.

  3. What it leaves behind

    Views, indexes, triggers and keys are left out. The tables and their rows come through, but these are not rebuilt in the merged file.

    For other conversions, see every SQLITE conversion.

Questions.What people ask about merging SQLITE files.

01OF 04

In the order you add them. Rows of tables with the same name follow that order, and the first file's columns come first.

They are stacked into one table. Columns are matched by name, and cells a table has no column for stay NULL.

No. Views, indexes, triggers and keys are left out of the merged database.

Not always. Columns take DuckDB's types, such as BIGINT, DOUBLE and VARCHAR. A table whose values do not match their column types is kept as text.