The SQL Collector for Monitor Server allows you to capture from the Adaptive Server Enterprise Monitor Server any currently executing SQL statements according to your user-defined criteria. Each SQL statement captured is categorized according to suspected levels of performance problem.
The SQL Collector for Monitor Server provides an easy way of viewing and analyzing any SQL statements currently running on the database server. You can specify your own criteria to use in selecting the SQL statements you want to view. Each SQL statement monitored is analyzed to see whether it is potentially problematic so that you can quickly determine which SQL statements may be causing the performance problem.
The SQL Collector window provides a work area for you to add and delete Collectors, storing information on the Collector name and description, number of SQL analyzed, start time, end time, and duration. It offers a way to view the monitored SQL statements. It displays the monitored SQL statement, corresponding query plan and related information such as server process ID (SPID), login name, capture time, and database name. You are able to copy problematic SQL statements to the SQL Optimizer for optimization.
SQL statements collected in Inspector files can be also be analyzed with the SQL Scanner module. Once you have identified potentially problematic SQL statements you can send the SQL to the SQL Optimizer, Index Advisor, the SQL Worksheet, or save them to the SQL Repository.
The SQL Collector for Monitor Server retrieves the SQL statements using the Adaptive Server Enterprise Monitor Server.
The SQL Collector for Monitor Server uses the Adaptive Server Enterprise Monitor Server to capture SQL statements that are currently running on the database. The following items need to be set before using the SQL Collector for Monitor Server:
You must have Adaptive Server 15.0 or later in order to have the Adaptive Server Enterprise Monitor Server.
The Monitor Server must be currently running. It must be configured on the same machine as the database server you want to monitor. With Dsedit, you can PING the remote Monitor Server to ensure that a connection is available from the PC.
The Adaptive Server and Monitor Server are defined in the \sybase\ini\sql.ini file on the client PC. The names in the SQL.INI file must match exactly the name of the Adaptive Server and the Monitor Server on the Database Server.
When adding a new Collector in the Add Collector window, the name for the Monitor Server must match exactly the name of the Monitor Server in the SQL.INI file.
The tempdb system segment should be at least 20 MB.
You must have sa_role privilege assigned to your logon.
ASE Parameter |
Description |
Recommended setting |
event buffers per engine | Specifies the number of events per database server that can be simultaneously monitored. | sp_configure "event buffers per engine", 2000 |
Specifies the maximum size in Kbytes of the SQL text monitored per connection. |
sp_configure "max SQL text monitored", 4096 | |
enable monitoring |
Disables the collection of performance statistics through the monitoring tables. |
sp_configure "enable monitoring", 0 |
Note: For details of how to configure Adaptive Server Enterprise Monitor Server to capture SQL statements, please refer to the Adaptive Server Manuals.
The SQL Collector for Monitor Server data directory is where the data files are created while executing the Inspect function. The data directory path is set in the Preferences window.
To review or change a directory
Click .
Select the Directory Setup tab.
The default setting for this directory is:
C:\Documents and Settings\User\Application Data\Quest Software\Quest SQL Optimizer\DATA
Changes to this directory cannot be made while the SQL Collector for Monitor Server is active.
Note: It is advisable not to change the data directory after you have used this function, as files created during monitoring are kept in this directory.
© ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center