Teratrax Performance Viewer
Teratrax Performance Viewer is the user interface of Teratrax
Performance Monitor. The Server Explorer on the left-hand-side allows
you to register your monitored SQL Server instances and connect to them
to analyze the various performance areas. If the server you are
registering is not configured to be monitored by Monitoring Agent, a
message is displayed asking you if you want to start monitoring this
server from the local copy of Monitoring Agent. If the local Monitoring
Agent is already monitoring a different server, you need to install
Teratrax Performance Monitor on a different computer (ideally, the
server you are registering) and configure Monitoring Agent to monitor
the new server from that computer.
Once the server is registered, you can connect to it and navigate to
various nodes in Server Explorer:
- Server Name: Selecting the main node of the registered
server displays information about the
system utilization of SQL
Server. The values displayed in this pane, such as CPU, memory, etc...
relate directly to the SQL Server instance. In other words, if CPU
utilization shows 30%, it means that SQL Server alone is using 30% of
the CPU time.
- Slow SQL Code: The Slow SQL Code
node provides a list
of slow SQL batches and stored procedures that took longer than the
defined minimum duration for Slow SQL Code to execute. You can set the minimum
duration value for captured SQL code from the Defaults tab in Monitoring Agent.
- Slow/Failed Jobs: The
Slow/Failed Jobs node lists all SQL Server Agent jobs that failed or
took longer than the defined minimum duration for Slow/Failed Jobs to
run. You can set the minimum
duration value for captured jobs from the Defaults tab in
Monitoring Agent.
- Process Blocking: The
Process Blocking node displays
information about SQL Server blocking and concurrency issues. By
default, Process Blocking is disabled.
Correlating data from the four panes in Teratrax Performance
Monitor provides you with information about potential bottlenecks in
your system and ways to solve them. For example, a slow running stored
procedure that happens to coincide with a spike in the CPU chart may
indicate that the stored procedure is performing a lot of calculations,
such as queries involving aggregates. Knowing this, you may decide to
tune your stored procedure code or increase the capacity of the
processors on the server. In another scenario, the same slow running
stored procedure may coincide with a surge in disk I/O, in which
case you may want to consider checking your index structure and/or
further normalization to the tables.
Related Links
Teratrax Monitoring Agent
Registering Server Instances
in Performance Viewer
System Utilization
SQL Server Blocking
Slow/Failed Jobs
Slow SQL Code
|
