The Log Analyzer database is getting really big. How can I reduce it's size?

The Log Analyzer creates a hit document for each hit recorded on the web site. After several days or weeks, the increasing number of documents in the database can cause the database to grow quite large. In most cases, after the hits are a few days old they are seldom examined individually. Hits are compiled into a Daily Summary every day. Most of the important information from the older hits is contained in these Daily Summaries, so the individual hits can usually be archived to another database, or purged (deleted).
If you set up either the purging or archiving function in the Global Configuration document, the older hit documents will be removed from the database automatically. This keeps the number of documents in the database from continuing to grow rapidly. The Daily and Period Summary documents will remain in the database.

Another cause of increased database size is views. Each view can take up quite a bit of space because it has to keep track of which documents it has indexed, which documents are included in the view, what order they are in, etc. This is stored in the "view index". When a view is opened for the first time, the view has to process all the documents in the database and create it's view index. Once created, the view index usually just stays in the database, taking up space. If the view is used only occasionally, this can be a poor use of space.
You can change the design of the views to discard the view index if it has not been used for a certain number of days. The trade-off here is that building a view index takes time. If the index has been deleted, it may take some time to build the index and open the view. You should consider which views are used frequently and which are used rarely when deciding whether to allow the view index to be deleted or not.