Using the Data Transfer Wizard¶
The Data Transfer Wizard guides you, step by step, through importing or exporting whole tables and views, with full control over the options at each stage. Use it for bulk transfers between SQLite databases, SQL scripts, and ADO data sources — for example, migrating a set of tables from one database to another, or scripting a database for backup or version control.
Open it with Import/Export → Data Transfer Wizard, then follow the pages to choose the direction of the transfer, the source or destination, the options, and finally the objects to transfer.
When a transfer hits an error¶
An object the destination will not take — a name it rejects, a bad line in a script, a path it cannot write — is reported in the log on the transfer page rather than as a crash, and the log's last line says what the run left behind: the changes rolled back, or kept, or nothing written at all when the failure came before the transfer began.
What happens next is the Continue on error option, on the options page:
- Off, which is how it starts, the transfer stops at the first error. Whether the objects that already went across are kept is then the Use transaction option's business: with a transaction the whole run is rolled back, without one they stay.
- On, the failing object is rolled back on its own — a table is a unit of its structure and then its rows — and the transfer carries on without it. The objects that were skipped are listed at the end, so a finished run still says what did not make it.
It is off by default deliberately: skipping past a failure changes what a finished transfer means, so it is yours to ask for rather than something to discover afterwards.
The option is not offered when importing a script. There the unit of work is a
statement rather than an object, and carrying on past a CREATE TABLE that
failed only produces a further run of errors about the rows meant for it.