I am having trouble compacting a database. The database was 38MB in size (I don’t even KNOW why it was that big, but anyway…). I compacted it like so:
load compact /mydbpath -D -B
This brought it down to 33MB, which is still way bigger than it should be. This DB is practically empty, and it is based on a template that is only 1.1MB. Why is my database so big and why isn’t it getting compacted?
The only out-of-the-ordinary thing I am doing with this DB is running “load design” on it alot. But that shouldn’t increase the size so much…should it?
You may have deletion stubs in the database. Typically by a database creation default it will leave it to the default of when to remove the document deletion stubs.
To know if you have this problem you can download NotesPeek from the sandbox to view if your application has deletion stubs.
To remove deletion stubs, click on Replication Settings for the database (right click on DB, choose Replication, then Settings…).
On the Space Savers tab (ND6), in the “Remove documents not modified in the last X days,” set it to ZERO (0). Do not check the checkbox next to it - you will lose many, if not all, docs!!!
Click OK.
When the window closes, go back into the Replication Settings and set the X days value back to 90 and once again, do not check the checkbox.
Click OK.
That will remove all the deletion stubs - you check with NotesPeek before and after to make sure.