On Wed, Apr 16, 2014 at 3:41 PM, Simon Slavin <slav...@bigfraud.org> wrote: > I would recommend that you download the SQLite shell tool and get to know it > a little. Not only is it useful in creating a SQLite database from an SQL > command dump or CSV files, but it allows you to test whether SQLite > understands your SQL commands or not (you might be using a trick that works > only in Postgres). If something works in the shell tool but not in your own > code, you know it's because of a bug in your own code.
I also recommend the shell tool. But note that there are tons of GUI tools for SQLite as well, although I suspect many (all?) may not like 5B rows ;) On Windows, I like SQLiteSpy, because it's simple and fast (Delphi based I believe). It didn't have a problem with DBs in the millions of rows (3-5M tops - a few 100s of MB) in my experience, but could be that 5B is too much to handle. In any case, if you do try SQLite GUI tools, and find one that works with such large DBs as you work with, I'd be very interested if you would share you experiences and share with all of us what works (or not!) on this list. TIA, --DD PS: Also look at https://sqlite.org/limits.html and http://www.sqlite.org/pragma.html. You can tune the page size of your DB (from 512B, 1KB to 64KB), and the cache size SQLite uses to avoid always reading stuff from disk. The default of 2,000 pages might be too low for your DB sizes and 16GB of RAM. An fast disk (SSD) would help too of course. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
