On 31 May 2011, at 8:18pm, Jan Hudec wrote: > At $work we have an application that processes *huge* (tens of millions of > rows in some of the larger tables, sometimes over 30GiB file size). This > application changes and when it does, it drops some tables and calculates > them again. What is somewhat surprising is that dropping the tables itself > takes quite long (order of minutes) time. > > - What is the reason it might take that long? I didn't expect removing the > table entry in sqlite_master and adding it's pages to the free list to > take that long.
Split the DROP into two stages: DELETE FROM myTable; DROP TABLE myTable; Which one takes all the time ? If it's the second one, then perhaps just delete all the records. Filling the table back up again with new rows obviously already takes considerable time so adding extra time may not be as inconvenient. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
