I have a Notes application that via an hourly agent imports data from an excell spreadsheet. The application works well, except the database size is increasing daily…right now it is 70meg in size - and the excell data is only 300k. I am running updall, fixup and compact every night with no results. Any help would be greatly appreciated.
Subject: Database size increasing
Be aware if your database has many views sorting in many columns your database can grow quite large (due to the view indexes).
Subject: Database size increasing
Going on the same topic as deletion stubs, you can minimize the replication time by setting a limit on the $Revision and $UpdatedBy fields in the database properties (advanced tab). Also, as noted in a previous post, check the view sizes. In the files tab of the admin client, right click on the file and select “manage views” which will specify how much space the views are attributing to the db size.
If this is a database used by many but the data does not require unread marks, disable those in the advanced properties as well.
Does this database have any reader and/or authors fields?
Alternatively, it may be some of the documents are not being displayed in the specified views. A quick way to validate is by selecting all in a common view and comparing that to the document count of the database properties.
The best way though is to code the exception to skip the document it exists in the database. This will minimize agent time, deletion stubs, and replication issues.
Looks like you got a team of people offering some great suggestions. Let us know if any of it helped.
Subject: Database size increasing
If you are continully deleting and replacing documents, you have to keep in mind that deletion stubs are being left behind – I would be willing to bet that most of the space in the database is being taken up by deletion stubs. You can reduce the purge interval in the database properties, but be careful – if anyone is replicating this database on an occasional basis, you may find that old documents pop up from time to time. A better idea might be to modify the existing documents rather than rip & replace.
Subject: RE: Database size increasing
Is there any way to get rid of the deletion stubs?
Subject: RE: Database size increasing
Subject: RE: Database size increasing
you can purge them but again old things will show up if/when users replicate…
Subject: RE: Database size increasing
Yes – via the purge interval. Again, be very careful with this – deletion stubs are there for a reason. They are how one replica knows that documents have been deleted in another replica.
Subject: RE: Database size increasing
This application is used for a web portal only - so I am only replicating between my 2 servers. Should I change the Remove documents not modified to be 0 0r 1 day?
Subject: Right now it is probably set to the default 90 days, I would recommend for your app 3 to 7 days.
Although the point about re-using the existing documents is very valid.
Subject: RE: Database size increasing
No – what if one of the servers is down for a few hours? 90 days may be more than you want, but 1 or 2 is genuinely begging for trouble. Howzabout, say, 15 or 30? Remeber that disk space is a heck of a lot cheaper than the time & effort needed to fix the database when it breaks.
Subject: RE: Database size increasing
What is the downside to changing the remove documents if not modified to just a few days??
Subject: RE: Database size increasing
Deleting all the documents in a database just to recreate mostly the exact same documents is just wrong. The way to avoid having millions of deletion stubs is to not create them in the first place. If the data hasn’t changed, leave the Notes document alone. If the data has changed, modify the document. Delete documents only if the source data with the matching key no longer exists.
Yes, it’s a more complex algorithm, but the sample database for this article has an agent you can copy from (Replicate Customers).
Bear in mind, if someone bookmarks a document in their browser, you don’t want to be deleting that document and giving it a new UNID.