Show TOC

Displaying the SQL Monitor LogLocate this document in the navigation structure

Prerequisites

  • You have the authorization profile to perform SQL Monitor administration tasks.

Context

Occasionally, you will need an overview of SQL Monitor activities within a certain period of time. The SQL Monitor log provides you, for example, with information regarding which server instance the SQL Monitor has been activated/deactivated on, or where the monitoring data has meanwhile been updated or deleted in the system by a user.

Target Audience
  • AS ABAP system administrators

Procedure

  1. Launch the SQL Monitor tool using the transaction code SQLM (/SDF/ZQLM for ST-PI version).
  2. Choose the menu item Start of the navigation path SQL Monitor Next navigation step Display Log End of the navigation path or click the corresponding button in the toolbar.
  3. In the screen that appears, specify the start date to restrict the time period for the history.
  4. To display results, press F8 or click the corresponding button in the toolbar.

Results

Figure 1: The History Gives an Overview of SQL Monitor Activities for a Certain Time Period

As a result, you get a list of actions or events such as activation or deactivation of the SQL Monitor, deletion of SQL Monitor records, and replication of data triggered by the periodic jobs, and so on.

For each action or event, the following detailed information is provided:
  • Start date and start time
  • Duration of action in milliseconds
  • User who performed the action
  • Servers involved
  • Transaction or program that triggered the action
  • Number of SQL Monitor records that have been executed on the database
  • Messages, including a link that refers to detailed log information
  • Status of action executed

When you proceed to analyze the SQL monitoring data, you can use this information, for example, to find out when the measurement was started or whether someone deleted the data records in the meantime.

In addition, you can use the history list to check for errors or performance issues that may have occurred while running the periodic SQL Monitor batch jobs.

Example

If, for example, the periodic data replication job consumes too much time, you can reduce the frequency of the job SQLM_UPDATE_DATA/SCHEDULE from once an hour (default setting) to once in four hours - for example.