GETTING STARTED
You can specify options on the Advanced tab in Database Properties to provide higher performance and functionality for specific uses. If the options in the Advanced tab are not visible to you, an administrator must change them for the database.
Don't maintain unread marks Maintaining unread marks in a database slows performance. For some databases, such as the Domino Directory or the Domino log file, unread marks are not useful. If you don't need to track read and unread documents, consider disabling unread marks in the database to improve performance.
Go to top
Optimize document table map Notes refers to tables of document information to determine which documents appear in an updated view. Selecting the "Document table bitmap optimization" property associates tables with the forms used by documents in each table. During a view update, Notes searches only tables whose views contain forms used by documents in that view. While there is a slight performance cost to maintaining this association, this setting speeds updates of small views in large databases significantly.
To enable optimization using the table-form association, select "Document table bitmap optimization." When you change this setting, compact the database to enable it. Make sure your system has sufficient disk space as this compact makes a temporary copy of the database. You can also use the load compact command with the -F or -f switch to enable or disable bitmap optimization.
Don't overwrite free space To prevent unauthorized users from accessing data, Notes overwrites deleted data in databases, which can reduce database performance. In some situations, this security feature is not necessary, such as when:
Maintain LastAccessed property Domino databases store the date when a document was last modified or read. By default, the database records only changes to documents -- not reads. If you select the database option "Maintain Last Accessed property," the database records reads of a document as well as changes to it. If you set the database to delete documents based on intervals without activity, such as 10 days without being read or modified, select "Maintain Last Accessed property" and be aware this may negatively impact database performance. Otherwise, leave the option deselected for best performance.
Disable transaction logging When disabled, this option turns off logging of all transactions for all Domino API functions. It also turns off full database integrity and a replacement of Database Fixup on system restart with high-speed transaction roll forward/rollback from transaction logs along with support for backup and recovery APIs.
Allow soft deletions The "Allow soft deletions" property lets deleted documents remain in the database and not be permanently removed for a set number of hours. The hours are set by the database manager in the Advanced tab of the Database Properties box. After the specified time period, the document is permanently deleted from the database. See Deleting and undeleting documents.
Don't support specialized response hierarchy Documents store information about their parent and response documents This information is used only by the @functions @AllChildren and @AllDescendants. In databases that don't use these @functions in views, select the database property "Don't support specialized response hierarchy" to improve database performance.
Don't allow headline monitoring Users can set up their headlines to search databases automatically for items of interest. If many users do this, database performance can be slow. To prevent a database from being monitored, select "Don't allow headline monitoring." See Subscribing to databases to receive the latest updates.
Allow more fields in database This option allows a database to contain up to 23,000 fields. For a database without this option selected, all field names when concatenated cannot exceed 64 kilobytes, which results in a database limit of approximately 3,000 fields.
Use LZ1 compression for attachments With Lotus Notes 6, you can compress attachments using the Lempel-Zev class 1 (LZ1) adaptive algorithm instead of the Huffman algorithm. Because LZ1 compression can save you a considerable amount of disk space, it is favored over the Huffman method. Be aware, however, that if you are working in an environment that uses different versions of client and server software and you choose this option, the attachments are automatically recompressed on the server using the Huffman algorithm. This recompression of attachments can add significant extra time to the process.
Limiting the number of entries in the $Updated By fields A document stores the name of the user or server that made each change to it in the $UpdatedBy field. This edit history requires disk space and slows both view updates and replication. If you do not need to maintain a complete edit history, specify the number of changes that the $UpdatedBy field tracks with the database setting "Limit entries in $Updated fields." Once the $UpdatedBy field reaches this limit, the next edit causes the oldest entry to be removed from the $UpdatedBy list.
Limiting the number of entries in the $Revisions fields A document stores the date and time of each change saved to it in the $Revisions field. Domino servers use this field to resolve replication or save conflicts. The $Revisions field stores up to 500 entries by default. If you do not need to track changes this closely, specify the number of changes that $Revisions field tracks with the database setting "Limit entries in $Revisions field." Once the $Revisions field reaches this limit, the next edit causes the oldest entry to be removed from the $Revisions list.
Consider limiting the entries in $Revisions fields in databases that:
Soft delete expire time in hours Allows the database manager to specify the time (in hours) that documents marked for "soft" deletion are held before they are permanently removed from the database.
See Also