TUNING
Regularly delete inactive documents from databases to save disk space, to make it easier for users to find information, and to improve database performance.
About this task
Table 1. Comparison of deletion methods
Note: Deletion stubs are markers that remain from deleted documents so that the documents are deleted in other replicas of the database.
For information on the document archiving tool, see the topic Specifying the computers where archiving runs and where the archive is stored in HCL Notes® Help.
In addition to these methods, you can also create an API program that deletes documents.
To archive deleted documents
If you have disk space available and you want users to be able to access deleted documents, archive the documents before deleting them. When doing so, follow these guidelines:
Procedure
1. Determine an archive frequency based on the type of database. For example, you might archive an infrequently accessed database, such as a company policy database, every three months. Archive a heavily used tracking database, such as a customer call-tracking database, once a month or once a week.
2. Notify users that you plan to archive the database.
3. In the About This Database document of the active database, post the archiving schedule and the location of the archive database.
4. Archive the database when it is not in use and server traffic is low -- for example, on Sunday night.
5. After archiving is complete and you've deleted documents from the active database, compact the active database.
6. If the database has replicas, replicate the active database when database use is light so that you minimize user interruptions.
7. Limit access to the archive database. Assign Manager access in the database ACL to one or two users and replicating servers. Assign Reader access in the database ACL to everyone else. By doing this, you ensure that view indexes and full-text search indexes update only when archiving occurs.
To customize an archive database for fast access
Using an archive database ensures that users can continue to access the archived data. Use any of these methods to make accessing the archive database fast and easy.
Note: Don't customize an archive database used by the document archiving tool.
Removing unnecessary fields makes the documents smaller and the views smaller and faster. For example, although the active database might include fields for the customer name, phone number, address, and fax number, the archive database might require only the customer name.
Using only a few views improves view performance by keeping the total size of the view indexes to a minimum. Providing a full-text index allows users to retrieve information easily.
Buttons and agents allow users to quickly open the archive database when necessary.
To analyze statistics within a database, create a view that generates statistics in an archive copy of the database. For example, in an archive copy of a Call Tracking database, create a view that generates totals for specific categories of call records and for all call records. Because archive databases usually contain data that span a long period of time, they are ideal for performing statistical analysis.
Related concepts Using an agent to delete and archive documents Controlling database size
Related tasks Creating an archiving policy settings document Limiting the contents of a replica Creating replicas using the Administration Process Scheduling server-to-server replication