Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The table below describes which Collector entities can be examined in the Activity tab.

Table 6- 1 Collector entities that can be examined in the Activity tab

Collector EntityDescription
DatabaseDisplays information on an activity in reference to a specific database.
ProgramDisplays information on an activity generated from a specific program. Displays 'N/A' if the program_name column in sysprocesses is null.
LoginDisplays information on an activity generated by a specific login. Displays 'N/A' if the suid column in sysprocesses holds a number for which the user name is null.
UserDisplays information on an activity generated by a specific user in the database in use.
MachineDisplays information on an activity generated from a specific workstation. If the hostname column in sysprocesses is null, displays the IP Address of the workstation for instances of version 12.5 or later, or 'N/A' for instances of earlier versions.

See Precise for Sybase agents on page 13.

...

The table below describes the additional information displayed in the Performance tab in the Association area.

Table 6- 2 Precise information displayed in the Performance tab

ColumnDescription
Entity Name (Such as Instance, Database)Displays the name of the entity.
In SybaseDisplays entity resource consumption (default: stacked bar chart) and shows entity breakdown during the selected time frame.
%Displays the percentage of the total In Sybase.
SessionsNumber of sessions that occurred during the selected time frame of the selected entity.
Duration (Avg)Average duration for a single session, in the selected entity during the selected time frame, calculated by dividing the Duration by the number of Sessions.
Statement ExecutionsNumber of statements executed during the selected time frame that were generated by the selected entity's sessions.
CPU Time

Cumulative CPU time for the entity during the selected time frame.

This value is calculated by the Collector agent as follows (this is an approximate value):

The CPU field in sysprocesses is sampled at the start point and end point. The value sampled at the start point is subtracted from the value sampled at the end point resulting in the CPU Time reported.

Physical I/O Operations

Cumulative number of physical I/O requests performed for the entity during the selected time frame.

This value is calculated by the Collector agent as follows (this value is an approximation):

The physical_io field in sysprocesses is sampled at the start point and the end point. The value sampled at the start point is subtracted from the value sampled at the end point resulting in the Physical I/O reported.

About viewing In Sybase data for Instance and Collector entities

...

The table below describes which performance and resource consumption information is displayed for the statement, batch, collapsed statement and collapsed batch entities.

Table 6- 3 Statement, Batch, Collapsed Statement and Collapsed Batch entities

EntityDescription
Statement

Displays information on the activity of a specific TSQL statement. A statement is always part of a batch.

When an encrypted stored procedure is encountered the statement will display Encrypted Text.

BatchDisplays information on the activity of a specific batch. A batch can either be a stored procedure, stored function, trigger, or a detailed batch. If it is a stored object, the name of the stored object is displayed.
Collapsed StatementRepresents similar statements that differ in their parameters (literals). In a collapsed statement, the literals are replaced with parameter markers. The collapsed statement lets you analyze the overall resource consumption of similar statements.
Collapsed BatchSimilar to collapsed statement a collapsed batch represents similar batches that differ in their parameters (literals). In a collapsed batch, the literals are replaced with parameter markers. The collapsed batch lets you analyze the overall resource consumption of similar batches.

See How information is collected on page 25.

...

The table below describes the additional information displayed in the Performance tab in the Association area.

Table 6- 4. Information displayed in the Performance tab

ColumnDescription
Image Modified
Click to launch the SQL tab with the selected entity, to continue your analysis of the selected statement or batch.
Entity NameDisplays the name of the entity (statement or batch).
In SybaseDisplays entity resource consumption (default: stacked bar chart) and shows entity breakdown during the selected time frame.
%Displays the percentage of the total In Sybase.
Statement ExecutionsNumber of statements executed during the selected time frame by the selected entity.
Statement Duration (Avg)Average duration for a single statement, in the selected entity during the selected time frame, calculated by dividing the Statement Duration by the number of executions.
TextDisplays the statement's text.

About viewing In Sybase data for Statement and Batch entities

...

The table below describes the additional information displayed in the Statistics tab in the Association area.

Table 6- 5 Information displayed in the Statistics tab

ColumnDescription
Image Modified
Click to launch the SQL tab with the selected entity, to continue your analysis of the selected statement or batch.
Entity Name (Such as Statement)Displays the name of the entity.
CPU TimeCumulative CPU time for the entity during the selected time frame.
Physical I/O OperationsTotal number of physical I/O requests performed by the selected entity during the selected time frame.
Parallel Sessions (Min)Minimum number of threads used to execute the statement or batch in parallel. This counter is calculated from the fid column in sysprocesses. This enables you to verify that Sybase is using the best execution plan for the current statement.
Parallel Sessions (Max)Maximum number of threads used to execute the statement or batch in parallel. This counter is calculated from the fid column in sysprocesses. This enables you to verify that Sybase is using the best execution plan for the current statement.

About viewing Plan data for Statement and Batch entities

The table below describes the additional information displayed in the Plan tab in the Association area.

Table 6-6 Information displayed in the Plan tab

ColumnsDescription
Image Modified
Click to launch the SQL tab with the selected entity, to continue your analysis of the selected statement or batch.
Entity Name (such as Statement)Displays the name of the entity.
DatabaseIdentifies the database on which the statement or batch is run.
User

Displays one of the Sybase users by whom this statement was executed.

If this statement is not part of a stored procedure, this user will be used as parsing user when explaining this batch.

Most Recent PlanIndicates the last time the access path of the statement or batch was changed.
Last Show PlanIndicates the last time the statement or batch was explained.
CostIndicates the total estimated cost of the statement's or batch's execution.
Table ScanIndicates whether a table scan was performed in the execution plan (applicable to Statement entity only).
Clustered Index ScanIndicates whether a clustered index scan was performed in the execution plan (applicable to Statement entity only).
Clustered Index SeekIndicates whether a clustered index seek was performed in the execution plan (applicable to Statement entity only).
Index ScanIndicates whether an index scan was performed in the execution plan (applicable to Statement entity only).
Index SeekIndicates whether an index seek was performed in the execution plan (applicable to Statement entity only).
Table LookupIndicates that a table lookup operation was performed in the execution plan (applicable to Statement entity only).
SortIndicates whether a sort operation was performed in the execution plan (applicable to Statement entity only).
Merge JoinIndicates whether a merge join operation was performed in the execution plan (applicable to Statement entity only).
JoinIndicates that a join (other than merge join) operation was performed in the execution plan (applicable to Statement entity only).
Nested Loops JoinIndicates whether a nested loops join operation was performed in the execution plan (applicable to Statement entity only).
Parallel AccessIndicates whether a parallel access operation was performed in the execution plan (applicable to Statement entity only).
Show Plan ErrirShows the error that occurred during the last explain process.

Collapsed Statement and Collapsed Batch entities Association area

...

The table below describes the additional information displayed in the Performance tab in the Association area.

Table 6- 7 Information displayed in the Performance tab

ColumnDescription
Entity NameDisplays the name of the Collapsed Statement or Collapsed Batch.
In SybaseDisplays entity resource consumption (default: stacked bar chart) and shows entity breakdown during the selected time frame.
%Displays the percentage of the total In Sybase.
OccurrencesNumber of different statements possessing the selected collapsed form.
Statement ExecutionsNumber of statements executed during the selected time frame by the selected entity.
Statement Duration (Avg)Average duration for a single statement, in the selected entity during the selected time frame, calculated by dividing the Statement Duration by the number of executions.
TextDisplays the statement or batch text, in the collapsed form.

In Sybase tab (Collapsed Statement and Collapsed Batch)

...

The table below describes the additional information displayed in the Statistics tab in the Association area.

Table 6- 8 Information displayed in the Statistics tab

ColumnDescription
Entity Name (Such as Collapsed Statement)Displays the name of the entity.
DatabaseIdentifies the database on which the collapsed statement or batch is run.
CPU TimeCumulative CPU time for the entity during the selected time frame.
Physical I/O OperationsTotal number of physical I/O requests performed by the selected entity during the selected time frame.
Parallel Sessions (Min)Minimum number of threads used to execute the statement or batch in parallel. This counter is calculated from the fid column in sysprocesses. This enables you to verify that Sybase is using the best execution plan for the current statement.
Parallel Sessions (Max)Maximum number of threads used to execute the statement or batch in parallel. This counter is calculated from the fid column in sysprocesses. This enables you to verify that Sybase is using the best execution plan for the current statement.

About Session and Blocker Session entities

...

The table below describes the additional information displayed in the Performance tab in the Association area.

Table 6- 9 Information displayed in the Performance tab

ColumnDescription
SPIDDisplays the system process ID. The SPID is a unique integer assigned to each user connection when the connection is made.
ProgramDisplays the program that opened the session.
In SybaseDisplays entity resource consumption (default: stacked bar chart) and shows entity breakdown over the specified time period.
DatabaseDisplays the database used by session.
LoginDisplays the Sybase login that opened the session.
Stat TimeDisplays when the session was started during the selected time frame.
Completed AtDisplays when the session was completed during the selected time frame.
MachineDisplays the machine the program ran on.
UserDisplays the database user that opened the session.
Duration (Summed)Displays the time that has elapsed since the login time.
Client Process IDDisplays the process ID of the program.

About viewing In Sybase data for Session and Blocker Session entities

...

The table below About viewing statistical data for Session and Blocker Session entities.

Table 6- 10 Information displayed in the Statistics tab

ColumnDescription
SPIDDisplays the system process ID. The SPID is a unique integer assigned to each user connection when the connection is made.
CPU TimeCumulative CPU time for the entity during the selected time frame.
Physical I/O OperationsTotal number of physical I/O requests performed by the selected session during the selected time frame.
Memory Pages UsedDisplays the memory consumed (in pages) by the selected session during the selected time frame.

See Understanding In Sybase session states on page 25.

...

  1. In the Instance list, choose the item you want to analyze.
  2. In the Time Frame list, choose the period of time you want to analyze.
  3. On the View controls in the Main area, click Scalability.
  4. In the Session Duration (Avg) vs. Sessions graph, observe the number of sessions and the impact of the average session duration, over the selected time period. For example, if you observe that average session duration decreases when the number of sessions increase, this may indicate that the application has a scalability problem.

 

...

  1. .

...

 

 

 

 

 

 

 

 

...