Page History
...
The Activity tab was designed to answer questions such as, "What happened yesterday, as well as a month ago and a year ago?" and "What has been the performance level of my applications over time.".
| Anchor | ||||
|---|---|---|---|---|
|
...
The Main area shows comprehensive information on the selected entity. You can choose from several views to examine the entity from different angles. For example, you can focus on an In Sybase over time graph for an Instance entity, to observe its resource consumption over time or you can focus on the Scalability view to investigate the scalability of the instance over time.
See About drilling down in context on page 18, About the Main area on page 17, and About the Association area on page 17.
Navigating in the Activity tab
...
Moving the pointer over the Tab heading displays a ToolTip with navigational information that traces the path you have already taken in your investigation
See See About drilling down in context on page 18, About the Main area on page 18, and and About the Association area on page 18.
About the Association area in the Activity tab
...
In the Association area, click the row of the program you want to view detailed information for. The Tab heading indicates the newly selected program; the Main area displays In Sybase information on the program you drilled down to, and the Association area shows information on statements executed by this program.
See See About drilling down in context on page 18, About the Main area on page 18, About the Association area on page 18, How most tabs are structured on page 15, Tasks common to most tabs on page 20, and About the Dashboard tab on page 33.
| Anchor | ||||
|---|---|---|---|---|
|
...
Displays instance grouping information for the selected Sybase Tier. It is possible to categorize instances into groups and observe their tuning counters, such as their In Sybase breakdown, according to the groups you defined. This option is useful if there are many instances in the same application. For an explanation on how to define instance groups, see the Precise Administration Guide.
About Instance and Collector entities
...
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 Entity | Description |
|---|---|
| Database | Displays information on an activity in reference to a specific database. |
| Program | Displays information on an activity generated from a specific program. Displays 'N/A' if the program_name column in sysprocesses is null. |
| Login | Displays 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. |
| User | Displays information on an activity generated by a specific user in the database in use. |
| Machine | Displays 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 following views are available for the Instance and Collector entities:
...
- Load. Displays information on the following session-related items:
- Sessions. Number of sessions that occurred during the specified time period of the selected collector entity. For example, if you are viewing the Login entity, this value represents the number of sessions that are connected to the selected Login.
- Duration (Avg). Average duration for a single session, in the selected collector entity during the selected time frame, calculated by dividing the Duration by the number of Sessions.
- Duration (Summed). Total amount of time that elapsed for all of the selected collector entity's sessions during the selected time frame.
- Statement Executions. Number of statements executed during the selected time frame that were generated by the selected collector entity's sessions.
- Statement Duration (Avg). Average duration for a single statement execution, in the selected collector entity during the selected time frame. This value is calculated by dividing the Duration (Summed) parameter by the number of statement executions.
- Statistics. Displays the following session-related statistics:
- CPU Time. Cumulative CPU time for the collector entity or instance during the selected time frame.
- Physical I/O Operations. Total number of physical I/O operations performed by all sessions connected to the database during the selected time frame.
- In Sybase Breakdown. Displays collector entity resource consumption (table format) and shows instance breakdown during the selected time frame. The table displays the following information:
- State. Displays the In Sybase state.
- In Sybase. Displays a graphical representation of the Time column.
- Time. Amount of time the selected collector entity was in this state.
- %. Percentage of time the selected collector entity was in this state
See About session states on page 25.
About viewing Instance and Collector In Sybase data
The In Sybase view displays the resource consumption of the selected collector entity during the selected time frame. This graph enables you to analyze performance trends for the collector entity, over time.
See “Understanding Understanding In Sybase session states” on page 25. See “Focusing on states and Focusing on information in overtime graphs” on page 22graphs.
About viewing Instance and Collector locking data
...
- Locks. Displays which sessions were involved in a blocking situation (either locking or blocking). It is important to understand which sessions are involved in each blocking chain, as there may be several sessions involved at the same time. It is then important to determine which session is blocking others, which object is being blocked, and what type of lock has been applied.
A yellow lock indicates that the session is currently blocking another session but is not itself blocked.
A red lock indicates the session is currently blocked by another session. Note that a session may also block other sessions while being blocked by a different session. - Lock wait graph. The Lock Wait graph shows a breakdown of the Lock Waits and when they occurred over the selected time period.
See Focusing on information in overtime graphs on page 22.
About viewing Instance and Collector overall activity
...
- Waitfor Command. The amount of time applications were waiting for a Waitfor command.
- Parallel Sync Wait. The amount of time applications were waiting on a synchronization message from another process in the family.
- Request Wait. The amount of time applications were in a Request Wait state, defined as the state wherein the server is waiting for a client request.
- Other Wait. The amount of time applications were in Other states.
- In Sybase. Represents total amount of time spent in Sybase.
See See Focusing on information in overtime graphs on page 22.
About viewing Instance and Collector scalability
...
- In Sybase (Avg) vs. Sessions. Compares the average In Sybase time of the selected collector entity with the number of sessions during the selected time frame. For example, if the selected collector entity is Login, the graph will show the number of sessions connected with the selected login versus the average In Sybase time of each session over time. Use this graph to analyze if the average session In Sybase time increases when the number of sessions increase.
See See Focusing on information in overtime graphs on page 22.
Instance and Collector entities Association area
...
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
| Column | Description |
|---|---|
| Entity Name (Such as Instance, Database) | Displays the name of the entity. |
| In Sybase | Displays entity resource consumption (default: stacked bar chart) and shows entity breakdown during the selected time frame. |
| % | Displays the percentage of the total In Sybase. |
| Sessions | Number 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 Executions | Number 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 |
| 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 |
About viewing In Sybase data for Instance and Collector entities
The In Sybase tab contains the In Sybase counter and the breakdown of the In Sybase into its states. The In Sybase is displayed with a normalized view while all the other counters display the time spent in each state.
See See Understanding In Sybase session states on page 25.
| Anchor | ||||
|---|---|---|---|---|
|
...
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
| Entity | Description |
|---|---|
| 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. |
| Batch | Displays 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 Statement | Represents 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 Batch | Similar 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 following views are available for the Statement, Batch, Collapsed Statement and Collapsed Batch entities:
...
The In Sybase view displays the resource consumption of the selected entity during the selected time frame. This graph enables you to analyze performance trends for the entity, over time.
See See Focusing on information in overtime graphs on page 22..
About viewing Statement, Collapsed Statement, Batch and Collapsed Batch entities locking
...
- Lock wait graph. The Lock Wait graph shows a breakdown of the Lock Waits and when they occurred over the selected time period.
See See Focusing on information in overtime graphs on page 22.
About viewing scalability for Statement, Collapsed Statement, Batch and Collapsed Batch entities
...
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
| Column | Description |
|---|---|
 | Click to launch the SQL tab with the selected entity, to continue your analysis of the selected statement or batch. |
| Entity Name | Displays the name of the entity (statement or batch). |
| In Sybase | Displays 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 Executions | Number 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. |
| Text | Displays 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
| Column | Description |
|---|---|
| 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 Time | Cumulative CPU time for the entity during the selected time frame. |
| Physical I/O Operations | Total 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
| Columns | Description |
|---|---|
| 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. |
| Database | Identifies 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 Plan | Indicates the last time the access path of the statement or batch was changed. |
| Last Show Plan | Indicates the last time the statement or batch was explained. |
| Cost | Indicates the total estimated cost of the statement's or batch's execution. |
| Table Scan | Indicates whether a table scan was performed in the execution plan (applicable to Statement entity only). |
| Clustered Index Scan | Indicates whether a clustered index scan was performed in the execution plan (applicable to Statement entity only). |
| Clustered Index Seek | Indicates whether a clustered index seek was performed in the execution plan (applicable to Statement entity only). |
| Index Scan | Indicates whether an index scan was performed in the execution plan (applicable to Statement entity only). |
| Index Seek | Indicates whether an index seek was performed in the execution plan (applicable to Statement entity only). |
| Table Lookup | Indicates that a table lookup operation was performed in the execution plan (applicable to Statement entity only). |
| Sort | Indicates whether a sort operation was performed in the execution plan (applicable to Statement entity only). |
| Merge Join | Indicates whether a merge join operation was performed in the execution plan (applicable to Statement entity only). |
| Join | Indicates that a join (other than merge join) operation was performed in the execution plan (applicable to Statement entity only). |
| Nested Loops Join | Indicates whether a nested loops join operation was performed in the execution plan (applicable to Statement entity only). |
| Parallel Access | Indicates whether a parallel access operation was performed in the execution plan (applicable to Statement entity only). |
| Show Plan Errir | Shows 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
| Column | Description |
|---|---|
| Entity Name | Displays the name of the Collapsed Statement or Collapsed Batch. |
| In Sybase | Displays entity resource consumption (default: stacked bar chart) and shows entity breakdown during the selected time frame. |
| % | Displays the percentage of the total In Sybase. |
| Occurrences | Number of different statements possessing the selected collapsed form. |
| Statement Executions | Number 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. |
| Text | Displays 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
| Column | Description |
|---|---|
| Entity Name (Such as Collapsed Statement) | Displays the name of the entity. |
| Database | Identifies the database on which the collapsed statement or batch is run. |
| CPU Time | Cumulative CPU time for the entity during the selected time frame. |
| Physical I/O Operations | Total 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
...
| Info |
|---|
The graph displays data in time slices. |
See See Understanding In Sybase session states on page 25. See and Focusing on information in overtime graphs on page 22.
About viewing Session and Blocker Session locking
The Locking view displays the blocking tree and the lock wait duration broken down into lock levels (such as, Table, Page, and Key) for the selected entity, over the selected time period. The following information is displayed:
...
| Info |
|---|
The graph displays data in time slices. |
See See Focusing on information in overtime graphs on page 22.
Session and Blocker Session entities Association area
...
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
| Column | Description |
|---|---|
| SPID | Displays the system process ID. The SPID is a unique integer assigned to each user connection when the connection is made. |
| Program | Displays the program that opened the session. |
| In Sybase | Displays entity resource consumption (default: stacked bar chart) and shows entity breakdown over the specified time period. |
| Database | Displays the database used by session. |
| Login | Displays the Sybase login that opened the session. |
| Stat Time | Displays when the session was started during the selected time frame. |
| Completed At | Displays when the session was completed during the selected time frame. |
| Machine | Displays the machine the program ran on. |
| User | Displays the database user that opened the session. |
| Duration (Summed) | Displays the time that has elapsed since the login time. |
| Client Process ID | Displays 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
| Column | Description |
|---|---|
| SPID | Displays the system process ID. The SPID is a unique integer assigned to each user connection when the connection is made. |
| CPU Time | Cumulative CPU time for the entity during the selected time frame. |
| Physical I/O Operations | Total number of physical I/O requests performed by the selected session during the selected time frame. |
| Memory Pages Used | Displays the memory consumed (in pages) by the selected session during the selected time frame. |
See See Understanding In Sybase session states on page 25.
| Anchor | ||||
|---|---|---|---|---|
|
...
- In the Instance list, choose the item you want to analyze.
- In the Time Frame list, choose the period of time you want to analyze.
- On the View controls in the Main area, click Scalability.
- 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.
Precise. Performance intelligence from click to storage. Learn more > >
...