Using latest 2.60 version, this export is very slow, as soon as you export more than few lines.
Replacing the ADO.NET destination by Script Destination make everything work, but make also dotconnectDriver useless for SSIS (the free SQLite driver is OK for that) !
It looks like a transaction is opened / closed for each INSERT, making huges amounts of disk access. Removing Journal File is useless.
SSIS export to SQLite3 using ADO.NET Destination
Changing "Synchronous" connexion option from "Normal" (default value) to "OFF" has resolved the problem.
I've been confused by SQLITE documentation, where default mode is OFF !
I would suggest you change the default synchronous mode to OFF, otherwise other customer will experience such performance issues, using SSIS.
I've been confused by SQLITE documentation, where default mode is OFF !
I would suggest you change the default synchronous mode to OFF, otherwise other customer will experience such performance issues, using SSIS.
Thank you for posting.
With Synchronous set to Off, SQLite continues without pausing at the most critical moments as soon as it has handed data off to the operating system. If the application running SQLite crashes, the data will be safe, but the database might become corrupted if the operating system crashes or the computer loses power before data has been written to the disk surface.
We will leave the default setting to Normal, and mention your experience in dotConnect for SQLite SQL Server Integration Services Tutorial.
With Synchronous set to Off, SQLite continues without pausing at the most critical moments as soon as it has handed data off to the operating system. If the application running SQLite crashes, the data will be safe, but the database might become corrupted if the operating system crashes or the computer loses power before data has been written to the disk surface.
We will leave the default setting to Normal, and mention your experience in dotConnect for SQLite SQL Server Integration Services Tutorial.