Home
HCL Domino Designer Basic User Guide and Reference
This guide provides information on using HCL Domino Designer and programming language reference information.
Application Management
Welcome to the Application Management section of Domino® Designer Help.
Procedure for optimizing and troubleshooting databases
Monitoring database activity
Monitor database activity regularly. If database activity is high and users report performance problems, do any of the following:

HCL Domino Designer Basic User Guide and Reference
This guide provides information on using HCL Domino Designer and programming language reference information.
- What's new in HCL Domino Designer 11 for developers?
  The following features are new for developers in HCL Domino® Designer 11.
- Accessibility and keyboard shortcuts
  Accessibility features assist users who have a disability, such as restricted mobility or limited vision, to use information technology content successfully.
- Application Design
  Welcome to the Application Design section of Domino® Designer Help.
- Application Management
  Welcome to the Application Management section of Domino® Designer Help.
  - Security in an application
    Domino® offers a multi-layered approach to security. Server administrators can secure databases, servers, and domains. Database designers and managers control the following:
  - Completing an application and managing design changes
    As you prepare to deploy an application, consider these finishing touches:
  - Deploying an application
    The tasks involved with application design, database design, database management, and DominoTMsystem administration may overlap, depending on the size of your organization and the structure of job responsibilities. In some organizations, an application developer may be responsible for both application and database design, while in others, a database manager may handle all database design and management tasks. In addition, database management overlaps with Domino® system administration.
  - Procedure for optimizing and troubleshooting databases
    - Properties that improve database performance
      Properly setting database properties can improve the performance of an active database. Setting database performance properties on many databases or on one, large, active database can also improve server performance. In addition, some of these property settings also help reduce the size of databases.
    - To set database properties that optimize database performance
    - Controlling database size
      Databases whose size is monitored and minimized show increased performance: database operations require less I/O and fewer CPU resources; view rebuilding and updating is quicker; and memory and disk space allocation is improved. The maximum database size is 64GB on Windows™ and UNIX™. Use the following methods to regularly monitor the size of databases and minimize database size:
    - Document archiving tool
    - Monitoring replication of a database
      If there are replicas of a database, use any of these methods to monitor replication daily.
    - Monitoring database activity
      Monitor database activity regularly. If database activity is high and users report performance problems, do any of the following:
      - Viewing database activity statistics generated by the Statlog task
      - Managing database activity recording in databases
      - Updating database indexes and views
        A view index is an internal filing system that Notes® uses to build the list of documents to display in a database view or folder. View indexes should be kept current so that information in views and folders stays synchronized with document updates.
    - Notifying users of a moved database
      After you move a database, create a new database with the same file name and path as the database before you moved it. In the new database, create a form and document that provides the following information:
    - Troubleshooting database performance
      You can reduce database performance problems by using:
    - Troubleshooting replication problems
      The following topics suggest solutions to common problems associated with scheduled replications.
- Domino® Query Language
  Domino® Query Language (DQL) is a facility running on a Domino server that provides a terse, shorthand syntax for finding documents. It supports a wide variety and complexity of search terms. It leverages existing design elements, avoiding the need to write detailed code to access them. DQL consolidates all methods in Domino for searching document contents.
- Composite Applications - Design and Management
  Composite applications are a key element in a service-oriented architecture (SOA) and contextual collaboration strategy. The ability to create and edit composite applications lets you easily integrate different types of components and technologies.
- DB2® Access views
  Domino® Designer includes two types of design elements to assist you in managing data contained in DB2® enabled Notes® databases:
- Programming Overview and User Interface
  This section contains general guidelines and examples that show where to use Java, LotusScript, and the formula language.
- Formula Language
  This section documents the formula language.
- LotusScript® Language
  Welcome to the LotusScript® Language section of Domino® Designer Help.
- LotusScript/COM/OLE Classes
- Java/CORBA Classes
  This section documents the Java/CORBA classes.
- Connectors
  Connectors provide native access to a wide variety of DBMS products, ODBC, the platform File system, Enterprise Resource Planning systems, and Transaction Processing systems.
- Javadoc™ for Domino® Designer related APIs
  As part of providing additional Java™ reference documentation, Domino® Designer ships with a help plugin that contains Javadoc™ for additional Domino Designer related APIs.

Monitoring database activity

Monitor database activity regularly. If database activity is high and users report performance problems, do any of the following:

Set database properties that improve 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.

Consider deleting an inactive database or view to free disk space on the server.

How the Statlog task generates activity statistics

The Statlog task runs by default once a day at 5 AM to report database activity on the server. The information appears as Database Activity Log entries in the Database - Usage and Database - Sizes views of the log file (LOG.NSF) and in the User Activity dialog box of individual databases. The Statlog task also reports database size statistics in the Database - Sizes view of the log file.

This table compares the information generated in each location.


Information provided	Appears in Database Activity Log entries	Appears in User Activity dialog box
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. Includes activity for anonymous and authenticated Internet clients.	Yes	Yes
Inactive views (indicated by the size 0)	Yes	No
Names of users and servers who read and wrote documents, sorted by date. Includes activity for anonymous and authenticated Internet clients.	No	Yes

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.

For information on File Monitor documents, the Event Monitor task, monitoring Web site activity, and monitoring database activity within a server cluster, see Domino® Administrator Help.