Easy solution to malformed SQLite databases

  1. ‹ Older
  2. 2 years ago

    Dave S

    4 Nov 2018 San Diego, California USA

    2.8.14 to 3.0.0 2004-06-18
    Version 3.0.0 is a major upgrade for SQLite that incorporates support for UTF-16, BLOBs, and a more compact encoding that results in database files that are typically 25% to 50% smaller. The new file format is very different and is completely incompatible with the version 2 file format.

    That is the last documented SQLite "structure" change I could find.
    Again the syntax for commands have changed, but that is just how data gets into and out of the database, once it is there, the structure is the same.

  3. Ralph A

    4 Nov 2018 Santa Monica, California

    @Ralph A Have you tried this one:


    They offer a free trial download that can at least let you see if it can preview the data. It just won't let you save to a new database.

    The reason i cited that one is that they claim it can repair header corruption.

  4. Emile S

    5 Nov 2018 Europe (France, Strasbourg)

    @Craig G I replaced the depreciated realSQLDatabase with SQLiteDatabase

    I do that too in 2013, and not long after the client ask some more Columns, so I added then, and in the same time I exported the db file contents from the REALSQLite format and import them into the brand new SQLite file format. I never had troubles with the db file in the last five years.

    How many file operations your DB File have ?
    Read: https://sqlite.org/fileformat.html

    • -> The Database Header
    • -> [24] File change counter.
  5. Tim S

    5 Nov 2018 Testers Canterbury, UK
    Edited 2 years ago

    @Craig G That's reassuring.
    Just trying to eliminate all possibilities.

    As I said before, the best place to ask and have answered questions about SQLite is on the SQLite Users' Mailing List:

    See: http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

or Sign Up to reply!