On this page:

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
14 rates

The Live View displays current activity for the database server. The live view shows key performance metrics for the last time period, which can be refreshed in a specified time interval between 10 seconds and 5 minutes. 

Access the Database Live Window

To access the Database Live Window

  1. To view a database's current performance, click the name of the database.
  2. Click the Live View tab.
  3. For clustered databases, select the node to view its details.

Features of the Database Live Window

On the Database Live Window you can:

  • Select the Auto Refresh box and then from the Every list, choose how often you want the system to update the live view.

  • Click the down arrow next to the database Collector name at the top of the page to choose to view the live view of a different database Collector by either selecting the database Collector name from the list or by searching for the database Collector by entering text in the search bar and then clicking the refresh icon to show only database Collectors that meet that search criteria.

  • Hover over the sections of the charts to see their details.

  • Click the View list to view All Active Sessions or All Sessions.
  • Click a column title on the Session List to sort the Session List using the clicked column as the sort key.

On the Database Live window you can see the following information:

  • CPU Usage: If you have enabled Hardware Monitoring for the server the chart shows the percentage of available CPU resources consumed by users and the system and a break down of how the CPU is being used.
    • IO - Disk input and output. 
    • System - Database operating system activities. 
    • User - User interaction with the database.
  • Memory Usage: Displays how much memory is in use and how much is available.
  • Query wait statesActivities that contribute to the time it takes the database to service the request. The wait states consuming the most time may point to performance bottlenecks. For example, db file sequential reads may be caused by segment header contention on indexes or by disk contention.
  • Session List: A table describing database usage instances and their properties. The database session is the application interaction with the database, a new session is started for each request. The columns displayed are database dependent.
  • Blocking Tree: A tree showing all the sessions causing blocks. Nested under each blocking session are the sessions being blocked and the corresponding queries and blocked objects.

For SQL Server, the CPU Usage and Memory Usage statistics are displayed in Live View even when hardware monitoring is disabled.

In the Live View for database clusters, you must select a node from the dropdown menu to view that node's activity.