Chatta subito con l'assistenza
Chat con il supporto

Foglight for SQL Azure 5.5.8.6 - User Guide

Introducing Foglight for SQL Azure Adding and Configuring Agents Reviewing SQL Azure Activity Reviewing Database Usage Reviewing the Database Properties Monitoring Estimated Costs Viewing User Metrics Using the Global Administration Options Reviewing Foglight for SQL Azure Alarms Glossary

Reviewing SQL Azure Activity

The Activity drilldown provides access to graphs that display both current and recent activity details for the currently monitored SQL Azure instance, as well as the instance’s bandwidth usage and the resulting estimated cost.
The first of this contains instructions regarding the use of the various panels of the Activity drilldown for carrying out a root-cause analysis of possible performance issues. The following provide in-depth data about each panel.

Viewing In-depth Data about the Instance

The Activity drilldown’s panels allow carrying out the following tasks:
•
Viewing statistics about current lock conflicts—using the Blocking (Current) panel, which displays information about all current blocked sessions and lock conflicts, including the connections and resources involved in these conflicts. For details, see Tracking Current Lock Conflicts on page 27.
•
Viewing statistics about historical lock conflicts—using the Blocking (History) panel, which displays all of the locks whose duration exceeded a predefined threshold during the selected time range. For details, see Tracking Historical Lock Conflicts on page 29.
•
Viewing session data—using the Sessions panel, which lists all current SQL sessions and allows viewing session details and locks. For details, see Viewing Detailed Sessions Data on page 30.
•
Viewing top SQL statements data—using the Top SQL Statements panel, which provides detailed information about the SQL statements that experienced the longest time of CPU consumption or highest number of total wait events during the specified time range. For details, see Tracking Top SQL Statements Data on page 34.
•
Viewing detailed statistics about the instance’s bandwidth usage—using the Bandwidth Usage panel, which provides detailed information about wait events, such as the maximum wait times for specific wait events. For details, see Monitoring Bandwidth Usage on page 37.

Tracking Current Lock Conflicts

The Blocking (Current) panel provides details for all current lock conflicts.
This panel allows carrying out the tasks detailed in the following :
•
Handling Blocking Sessions, using the Blocking table. For details, see Handling blocking sessions.
•
Monitoring the processes blocked during the reporting period, using the Number of Blocked Processes chart. For details, see Monitoring blocked processes for the sampled interval on page 29.

Handling blocking sessions

The Blocking table displays all connections that are either currently waiting on locks held by others, or are causing others to wait, highlighting who is waiting on whom, and the resources involved.
 
* 
IMPORTANT: To create a custom filter for this table, use the options accessible by clicking the Customizer button at the table’s upper right side. For details, see Components Shared by all Foglight for SQL Azure Screens on page 13.
The hierarchy in this tree diagram represents the blocking chains. It shows who is blocking whom, by displaying one entry for each session that is blocked, and one for each session that is blocking another but is not blocked itself. Sessions at the top of the tree (those that do not have a parent in the tree) are at the head of the blocking chain, and are therefore the root cause of all blocking. Such sessions appear as Lead Blockers in the Number of Blocked Processes chart.
 
Table 1. The Blocking Table with Parameters
Parameter
Description
SPID
The session unique identifier (Session Process ID).
The unique number the Server has assigned for identifying the selected session, which owns or requests the lock.
Blocked Session ID
The unique identification of the session that is blocking the selected session.
Database Name
The name of the monitored database.
Status
The status of the session (Blocked, Blocking or both). For lead blockers (sessions that are not blocked), this will also indicate if the session is Runnable or Sleeping
Wait Resource
The ID of the resource to which the session is waiting.
Object Resource
The resource that is in contention. This often identifies a database and table.
The data in the Object Resource column is reported directly from SQL Azure and, for performance reasons, is not resolved to actual resource names during normal data collection.
Wait Time
Indicates how long this session has been waiting for the lock (measured in seconds). If the value displayed is 0, the session is not waiting.
Open Resultsets
The number of open result sets, namely: SQL batches running on an open connection at the same time.
A high value of this parameter can indicate that a large amount of data is not yet released, resulting in wait events.
Open Transactions
The number of open transactions.
A high value of this parameter can indicate that a large amount of data is not yet released, resulting in wait events.
CPU
The total amount of CPU consumed by the session so far.
This data can be useful when deciding which sessions to kill.
Memory Usage
The amount of Memory in MB used by the session.
Logical Reads
The amount of logical reads, in MB, carried out so far by the selected session.
Physical I/O
The total amount, in MB, of physical I/O resources consumed by the session so far.
This information can be useful when deciding which sessions to kill.
Lock Level
The type of the resource that is currently being locked (Page, Extent, Row, Range, Table, Database).
Lock Mode
The kind of lock being applied to the resource (Shared, Exclusive, Update, IntentShared, IntentExclusive, and so on).
Lock Status
The status of the lock. This status can have one of the following values:
•
WAIT—Wait for another resource
•
CNVT—Converted to another resource
•
GRANT—the lock has been granted
SQL Text
The text of the SQL statement executed by the session that is blocked and/or blocking.
NOTE: The columns detailed below are not displayed by default, and need to be selected for display via the Customizer button. For details, see Components Shared by all Foglight for SQL Azure Screens on page 13.
Physical Reads
The amount of physical reads, in MB, carried out so far by the selected session.
Physical read operations are necessary when accessing new table or index pages. Nevertheless, these operations should be avoided when possible, as requested pages should reside in the SQL Azure buffer cache.
Physical Writes
The amount of physical writes, in MB, carried out so far by the selected session.
Program Name
The name of the application currently being used (for example, Microsoft Access).
Host Name
The name of the Client computer.
SQL User
Identifies the user associated with the SPID.
OS User
Windows user name for the process.
NOTE: In SQL Azure, which does not use Windows Authentication or a trusted connection, this column holds no value.
Requestor Ref. Count
The number of times the same requestor has requested a resource.
Isolation Level
The isolation level used for the current request or session, namely: the level at which transactions are protected from being affected by data or resource modifications carried out by other transactions.
The possible values are as follows:
•
Read uncommitted
•
Read committed
•
Repeatable read
•
Serializable
Lock Timeout
The amount of time that this session will wait for lock requests to be satisfied; corresponds to the @@Lock_Timeout global variable for this session.
Last Row Count
The number of rows affected by the most recently executed SQL statement.
Command
The current or previous command that was executed.
This information can be useful when deciding which sessions to kill.
Lock Type
The actual lock type (wait event) SQL Azure is using or intends to use.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione