• Set database properties that optimize performance.
• Create a replica of the database on another server, if possible, one within a server cluster.
• Move the database to a more powerful server.
• Move the database to a disk that is less heavily used, or if it's a large database, to its own disk.
• Track database activity with activity logging.

How the Statlog task generates activity statistics

The Statlog task on a server runs by default once a day at 5 AM, at which time it reports database activity for databases on the server in Database Activity Log entries in the Database - Usage and Database - Sizes views of the log file (LOG.NSF) and to the User Activity dialog box of individual databases. This table compares the information generated in each location.

Information provided	Database Activity Log entry	User Activity dialog box
Shows total number of times user and servers accessed, read, and wrote to a database in past 24 hours, past week, past month, and since the creation of the database*	Yes	Yes
Shows inactive views (indicated by the size 0)	Yes	No
Shows names of users and servers who read and wrote documents, sorted by date*	No	Yes

* Includes activity for anonymous and authenticated Internet clients.

Tip In addition to viewing activity statistics reported by Statlog, you can evaluate database activity by creating a view that sorts documents by date. You can also create File Monitor documents as part of Event Monitor configuration. File Monitors report user activity for specific databases.

Note The Statlog task also reports database size statistics in the Database - Sizes view of the log file.

Related topics

Database properties that optimize database performance
Moving databases
Notes database activity logging
Viewing database activity statistics generated by the Statlog task
Managing database activity recording in databases

Glossary