User Interface
Teratrax Performance Viewer allows you to
register an unlimited number of SQL Server instances and connect to
them to view and analyze performance information. You cannot register an
instance that is not monitored
by Teratrax Performance Agent.
Server Explorer Nodes
- Server Name: Selecting the main node of the registered
server displays information about the
system utilization of the SQL
Server instance. 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 this SQL Server instance alone is using 30% of
the CPU time.
- Slow SQL Code: Provides a list
of slow SQL batches (including stored procedure calls) and RPC events that took longer than the
defined minimum duration for Slow SQL Code in
Teratrax Performance Agent.
- Process Blocking: Lists the blocks
occurring on the SQL Server instance and the applications
that are causing them. By
default, process blocking is disabled. You can enable and configure
process blocking from Teratrax
Performance Agent.
- Deadlocks: Lists the deadlocks
occurring on your SQL Server instance.
- Slow/Failed Jobs: Lists SQL Server jobs that failed or
took a long time to run. You can set the minimum
duration value for captured jobs in
Teratrax Performance Agent.
- Connections: Lists current user
connections and information about each connection.
- Open Transactions: Lists current
open transactions and information about each process with an open
transaction.
- Failed Logins: Lists failed login
attempts made against the SQL Server instance.
- Alerts: allows you to create and manage
various types of e-mail alerts.
Correlating data from the various panes in Teratrax Performance
Viewer 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, you can correlate the
processes of blocks with those of deadlocks and slow SQL code to get a
better understanding of the events leading to a deadlock.
|
