サポートと今すぐチャット
サポートとのチャット

SQL Optimizer for SAP ASE 3.8 - User Guide

Introduction Tutorials Preferences Editor Functions SQL Information and Functions Performance Monitor SQL Inspector SQL Collector for Monitor Server SQL Scanner Index Advisor SQL Optimizer
SQL Optimizer Overview Optimization Engine Common Coding Errors in SQL Statements What Function Should l Use to Retrieve the Run Time? Unsatisfactory Performance Results SQL Optimizer Functions SQL Editor Optimized SQL Activity Log
SQL Worksheet SQL Formatter Database Explorer Code Finder Object Extractor SQL Repository Index Impact Analyzer Index Usage Analyzer Configuration Analyzer Migration Analyzer Abstract Plan Manager User-Defined Temp Tables SQL History Legal Information

Monitor Process

SQL Collector for Monitor Server > Add or Modify a Collector > Monitor Process

The Monitor Process page consists of the following settings:

Item Description

Whole Server

Monitor all SQL statements currently running from the database server.

Process ID

Monitor all SQL statements currently running which have the specified process ID (spid). The Process ID grid displays information about all current users and processes of the database server, displaying the process ID (spid), login name, host name, database name and the command currently executed (cmd). Click the row of the grid to select the process ID you want to monitor. To select all the process IDs, simply click the Select All checkbox.

Connection Identity

Monitor all currently running SQL statements with specified login name, host name, database name and program name.

 

Related Topic

Collecting Criteria

SQL Collector for Monitor Server > Add or Modify a Collector > Collecting Criteria

The Collecting Criteria page has the following settings:

Section

Item

Description

SQL Type All SQL Monitor all SQL statements currently running.
Selected Type To monitor the selected SQL classification type (Problematic or Complex).

Complex Range

Number of table scan operations

Specify the range of numbers for the table references in the query plan for Complex SQL statement definition.

With full index scan

Specify whether SQL statements with full index scan will be classified as Complex SQL statements.

Problematic Range

 

 

With full table scan

Specify whether SQL statements with full table scan will be classified as Problematic SQL statements.

With number of worktables greater than or equal to

(Range = 1 to 99)

Specify that SQL statements involving the number of worktables greater than or equal to the defined number are classified as Problematic SQL statements.

With number of Reformattings greater than or equal to

(Range = 1 to 99)

Specify that SQL statements whose query plan uses reformatting are classified as Problematic SQL. Reformatting is the process of generating a worktable with a clustered index and performing a nested-loop join. The Adaptive Server optimizer may choose this strategy when the table is large and does not have any useful index for a join.

Note: The default settings for the values are taken from the SQL Classification tab in the Preferences window.

 

Related Topic

Schedule Settings

SQL Collector for Monitor Server > Add or Modify a Collector > Schedule Settings

The Schedule Settings page consists of the following settings:

Item Description

Start Time

Monitor start time. Default is the current time.

Until (time)

Monitor end time. Default is 5 minutes after the start time.

Until (Duration)

Monitoring duration in hours and minutes. Default is 5 minutes.

Interval

Monitoring interval time in seconds. Default is 3 seconds.

Notes:

  • Decreasing the interval time may affect the database server performance and network traffic.
  • The ad-hoc monitoring from the right-click menu does not use the start, until, and duration time. Monitor will start immediately and is terminated by clicking Abort Monitor.

 

Related Topic

Query Plan

SQL Collector for Monitor Server > Query Plan

SQL statements captured in the SQL Collector for Monitor Server modules are displayed with corresponding query plan using the sp_showplan stored procedure. If the query plan is not available, then the Query Plan pane window remains blank and the SQL is classified as SQL without Plan

Note: It is not guarantee that using the sp_showplan stored procedure to retrieve the query plan will obtain a query plan that corresponds to the SQL statement.

 

Related Topic

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択