| Unread Mark Options: Don't Maintain Unread Marks | Some databases may not need to track unread documents, and disabling this feature increases performance and reduces database size. You can also disable views from displaying unread marks, but this results in no performance improvement. The database must be compacted for this setting to take effect. |
| Advanced Option: Optimize Document Table Map | Using only the forms referenced by the documents contained within each view, this option associates only the tables using the document forms to update each respective view, thus increasing performance. Internally, Domino maintains tables containing information about documents contained within each view. These tables are used when the view indexes are updated or rebuilt. If the views contain selection formulas that specify which forms to use (for example Form=“Main Document”, enabling Document Table Bitmap Optimization optimizes performance by using only the tables that use the forms specified in the view selection formula. |
| Don't Overwrite Free Space | As a security feature, Domino automatically overwrites deleted data with new data, ensuring that deleted data cannot be recovered. This causes additional I/O operations to the disk. Selecting this option increases performance, but alternative security options should be considered. |
| Maintain LastAccessed Property | When enabled, Domino tracks who last read the document. Disabling this option causes Domino to track only who last modified each document, thus minimizing disk I/O operations and increasing performance. |
| Disable Transaction Logging | After transaction logging has been set up, all database transactions are logged. Disabling this feature by making this selection increases performance but is generally discouraged because it makes it more difficult to recover from system failures. This is the better option to use on non-critical databases such as help databases or databases in which the data doesn't change very often. |
| Don't Support Specialized Response Hierarchy | Disabling this feature reduces the information stored to support certain @Functions used in views to display response documents (specifically, the @AllChildren and @AllDescendants functions). Therefore, this setting improves application performance and slightly reduces the database size. Views and replication formulas that do not use these two functions still display response documents as intended. The database must be compacted for this setting to take affect. |
| Use LZ1 Compression for Attachments | The new enhanced compression method available with Domino 6. This increases the performance when downloaded, uploaded, or opening attachments. When enabled, Domino uses LZ1 compression. |
| Don't Allow Headline Monitoring | When selected, prevents users from using headline monitoring for the database. Restricting the user of headline monitoring improves performance. |
| Soft Delete Expire Time in Hours | Soft deletions allow for deleted documents to be held in the database for the specified amount of time before being deleted. Reducing the time deleted documents are held minimizes database size and helps improve performance. |
| Limit Entries in $UpdatedBy Fields | Enables you to limit the number of entries in the $UpdatedBy field. This field contains the canonical name of each person or server who has edited the Notes document. If each document has a lot of activity and many modifications, reducing the number of revisions tracked per document can increase performance and reduce database size. When the limit is reached, the oldest entry is removed. |
| Limit Entries in $Revisions Fields | Enables you to limit the number of entries in the $Revisions field, thus increasing application performance and reducing database size. This field contains the date and time each Notes document was edited. If each document has a lot of activity and many modifications, reducing the number of revisions tracked per document can increase performance. When the limit is reached, the oldest entry is removed. By default, this field contains up to 500 entries. Because each entry requires 8 bytes of disk space, the larger this field becomes, the slower the database performance. Because this field is used to resolve replication or save conflicts, this value should never be set to less than 10. |
