On 1/16/15, MikeD <supp...@dotysoftware.com> wrote: > I have a database that has become 28,268,814,336 bytes so > downloaded the sqlite3_analyzer and it has been running for over > 15-minutes. > > Task manager shows sqlite3_analyzer.exe using 13% and the memory stays > steady at 23,768K. > 19 handles, 1 thread(s). > > The database was a test database that has been used for some time. > I can't say when the file became huge. Vacuum was occassionaly run. > > Just terminated sqlite3_analyzer.
That's too bad, because if you had let sqlite3_analyzer run to completion, it would have output some very useful information about the state of the database file. > Vacuum memory usage is between 11 and 13 percent using 24,564K. > I'll let vacuum continue to run. It has been running 15-minutes. > > The database is still working. What should I be doing? > > > > > > -- > View this message in context: > http://sqlite.1065341.n5.nabble.com/Database-corrupted-28-billion-bytes-tp80048.html > Sent from the SQLite mailing list archive at Nabble.com. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
