 |
 |
View all applications currently connected to the server and see what commands are running. |
|
 |
End applications and processes connected to the
server to free up resources. |
|
 |
Immediately see how many connections there are to the
server, how many processes are running and the total CPU time used since the
server was started. |
|
 |
See which NT and SQL Server users are connected to
the server, how much CPU, disk I/O and memory each process is consuming and end
processes. |
|
 |
Instantly see how many connections there are to each
active database on the server. |
|
 |
End all connections to a database so it can be taken
offline or the server can be restarted. |
|
 |
View how much CPU, disk I/O and memory is being
consumed by all the connections to each database. |
|
 |
See how many open transactions there are on any
database and how long it has been since a command was executed against the
database. This makes it easy to stop the server or take the database offline if
no connections are actually active. |
|
 |
Immediately see all the T-SQL and stored procedures
running against active database and how many times each has been executed.
Quickly find queries being repeatedly executed that can be converted to stored
procs so execution plans will be created. |
|
 |
Discover how many bytes and how many pages queries
are using and locate troublesome T-SQL statements that are consuming too much
server resources and need tuning. |
|
 |
Keep databases secure by seeing in an instant which
users are connected to the server. Find out when each user was last active and
how much time has passed since the user ran a query against a database. Inactive
connections can then be killed off. |
|
 |
Instantly see how much disk I/O SQL Server is using,
the total number of reads, writes and errors on the disk. |
|
 |
Monitor network activity and see how many packets are
being sent to and from the server and how many errors are occurring. |
|
 |
Make capacity planning easy – see how much load is
being put on the server and each database in turn. And find out which queries
and applications consume the most resources. |
|
 |
Determine if heavily used databases should be moved
to another server or if hardware upgrades are required. |