Chat now with support
Chat with Support

Foglight for SQL Server (Cartridge) 5.9.4.10 - User Guide

Introduction to this Guide Using Foglight for SQL Server
Viewing the Databases Dashboard Overview Dashboard Advisories Dashboard Monitoring Data Replication Monitoring SQL Performance Reviewing Memory Usage Reviewing the Instance Activity Reviewing Database Usage Reviewing the Services Using the HADR Drilldown Using the Logs Drilldown Reviewing Configuration Settings Viewing User-defined Performance Counters and Collections
Monitoring Business Intelligence Services Administering Foglight for SQL Server
Configuration Settings Managing Foglight for SQL Server Agent Settings Reviewing Foglight for SQL Server Alarms Generating Reports Monitoring SQL Server instances on VMware servers
Glossary
A
Access methods Adhoc SQL Plans Alarm Alert Allow updates Anonymous subscription Authentication AutoClose AutoGrow Automatic Discovery AutoShrink B Batch BCP (Bulk Copy Program) Blocking Books Online Bound trees Buffer Buffer cache Buffer pool Bulk copy Bulkinsert Bulk load C Cache CAL Calibration Cardinality Cartridge Chart Checkpoint process Client network utility CLR Compile Connect Connection Connectivity software CPU Usage Cursors D Data access components Data file Data storage engine Database Database object DataFlow DBCC DBID DBO Deadlock Disk queue length Disk transfer time Disk utilization DiskPerf Distributing instance Distributor DMO Drilldown DTC DTS E Error log Event alert Execution contexts Extended stored procedures Extent External procedures F File Filegroup File cache Foglight Agent Manager Foglight Management Server Foreign key Forwarded records Free buffers Free list Free pages Free potential Free space Freespace scans Full text search G GAM Ghosted records Growth increment GUID H Hash buckets Hashing Heap Hit rate Hit ratio Host name Host process I I/O Index Indid Integrated security Intent Locks J Job K Kernel memory Kernel mode Kill L Latch Lazy writer Licensing Lightweight pooling Lock Lock area Lock escalation Lock mode Log Log cache Log writer Logical I/O LRU LSN M Master MaxSize MDAC Metric Misc.normalized trees Model Monitor page file N Named pipes Net library NIC Null O OBID Object plans OLAP OLAP service OLTP Optimizer Optimizer cache osql P Page life expectancy Paging Panel Parse Parser Per seat licensing Per server licensing Performance alert Physical I/O Physical read Physical write PID Pinned Plan Plan cache Potential growth Prepared SQL plans Primary key Privileged mode Procedure cache Procedure plans Process Profiler Publication database Publisher Publisher databases Publishing server Pull subscription Pulse Push subscription Q Query plan R RAID Random I/O Read ahead Recompile Referential integrity Relational data engine Replication procedure plans Role Rollback S sa Schema locks Sequential I/O Session Severity SGAM Shared locks Show advanced options SMP Sort, Hash, Index Area SPID Spike Spinner SQL Agent Mail SQL Mail SQL Plans SQL Server Agent SQL Server authentication SQL Server books online Standard deviation Stolen pages Stored procedure Support service SYSADMIN role T TDS TempDB Temporary tables and table variables Threshold Torn page detection Transaction Trigger Trigger plans Truncate Trusted U UMS Unused space User connection area User mode V Virtual log file VLF W Waitfor Windows authentication mode Working set
Reference
SQL PI Repository Cold Backup Procedure SQL Performance Investigator Metrics
Active Time All SQL Agents CPU Usage All SQL Agents Resident Memory Usage Availability Average Physical I/O Operations Average SQL Response Time Backup Recovery Wait Blocked Lock Requests Checkpoint Pages CLR Wait CPU Usage CPU Wait Cursor Synchronization Wait Database Replication Wait Deferred Task Worker Wait Degree of Parallelism Disk Utilization DTC CPU Usage DTC Resident Memory Usage Distributed Transaction Wait Executions Ended Executions Started External Procedures Wait Full Scans Full Text Search CPU Usage Full Text Search Resident Memory Usage Full Text Search Wait Free Buffer Wait Hosted Components Wait IO Bulk Load Wait IO Completion Wait IO Data Page Wait IO Wait Latch Buffer Wait Latch Wait Latch Savepoint Wait Lazy Writes Lock Wait Lock Bulk Update Wait Lock Exclusive Wait Lock Intent Wait Lock Requests Lock Schema Wait Lock Shared Wait Lock Update Wait Lock Wait Log Buffer Wait Log Flushes Log Other Wait Log Synchronization Wait Log Wait Log Write Wait Memory Wait Network IO Wait Network IPC Wait Network Mirror Wait Network Wait Non SQL Server CPU Usage Non SQL Resident Memory Usage OLAP CPU Usage OLAP Resident Memory Usage OLEDB Provider Full Text Wait Other CPU Usage Other Miscellaneous Wait Other Wait Overall CPU Page Life Expectancy Page Splits Parallel Coordination Wait Physical I/O Physical Memory Used Physical Page Reads Physical Page Writes Probe Scans Plan Cache Hit Rate Range Scans Rec Ended Duration Remote Provider Wait Run Queue Length Samples Service Broker Wait Session Logons Session Logoffs SQL Agent CPU Usage SQL Agent Resident Memory Usage SQL Executions SQL Mail CPU Usage SQL Mail Resident Memory Usage SQL Recompilations SQL Response Time SQL Server Background CPU Usage SQL Server Cache Memory SQL Server Connections Memory SQL Server Connections Summary SQL Server Foreground CPU Usage SQL Server Resident Memory Usage SQL Server Swap Memory Usage Synchronous Task Wait Table Lock Escalation Target Instance Memory Total CPU Usage Total Instance Memory Virtual Memory Used
Rules Collections and Metrics

Mirroring Table

The Mirroring table displays the columns listed below.

The table below provides data about the columns that appear by default in the table. For a list of additional metrics, which are hidden by default, see Additional metrics in the Mirroring table .

 
Table 58. Mirroring table, default columns:
Column
Description
DBID

A number (ID) uniquely identifying a database within a SQL Server.

Database

The database name.

NOTE: The database name appears as a link which, when clicked, displays the Databases drilldown in Overview mode, with the selected database highlighted in the Databases table and its details displayed in the panes below.
Mirroring Role

The role the database takes in the mirroring process; either principal or mirror.

NOTE: The mirroring role is displayed as a link which, when clicked, displays the mirroring performance history of the selected database. For details, see Viewing the Selected Database’s Mirroring Performance History .
Principal

The name of the instance whose role in the process is principal.

Mirror

The name of the instance whose role in the mirroring process is mirror.

Mirroring Status

Indicates the severity determined based on the database state: Normal, Warning, or Critical. Each of these severity level values can correspond to several mirroring states.

Normal — can correspond to one of the following mirroring states:

•
SYNCHRONIZED (with a Witness)
•
SYNCHRONIZED (without a Witness)
NOTE: To view whether the mirroring operation is configured to use a Witness, click the Customizer button at the end of the table and turn on the display of the Witness Name and Witness State columns. For details, see Additional metrics in the Mirroring table .
•
SYNCHRONIZING

Warning — can correspond to one of the following mirroring states:

•
DISCONNECTED
•
PENDING_FAILOVER

Critical — can correspond to one of the following mirroring states:

•
SUSPENDED
•
UNSYNCHRONIZED
Mirroring State

A state indicating the mirroring session condition. This field can have one of the following values:

•
DISCONNECTED
•
SYNCHRONIZED (with a Witness configured)
•
SYNCHRONIZING
•
PENDING_FAILOVER
•
SUSPENDED
•
UNSYNCHRONIZED
•
SYNCHRONIZED (without a Witness configured)
Safety Level

The safety level at which the mirroring session is configured to work. This column indicates the level of synchronization between the two servers that take part in the mirroring process.

This field can have one of the following values:

•
UNKNOWN — unknown state
•
OFF — high availability (asynchronous). When an instance is configured with this safety level, the main consideration is that it remains available, regardless of the availability of its mirroring partner.
•
FULL — high safety (synchronous). The instance is configured to fail over when its mirroring partner becomes unavailable. Failover can be carried out automatically (if a Witness is configured) or manually.
Redo Queue

The redo queue size. This size can be either left Unlimited or defined in megabytes (MB).

Alarms

The number of warning, critical, and fatal alarms for the SQL Server database instance. When holding the cursor over one of the alarm counts, the dwell displays the most recent alarms raised against this database, sorted by severity.

Clicking this field displays the Alarms list, which is listed by severity order. See the Foglight Online Help, Monitoring System-Wide Alarms for details on the alarm information.

Additional metrics in the Mirroring table

The metrics listed below, which are also part of the Database Mirroring collection, do not appear by default in the Mirroring table. For details on these metrics, see the Database Mirroring Collection section in Foglight for SQL Server Reference Guide.

To display the metrics listed below:
1
Click the Customizer button () at the end of the table.
2
Select the check box near the requested metric.
Additional metrics list
•
Failover LSN
•
End Log LSN
•
Replication LSN
•
Witness State
•
Connection Timeout
•
Partner Name
•
Witness Name
•
Role Sequence
•
Log Scanned For Undo
•
Log Remaining For Undo
•
Mirroring Roundtrip - Latency
•
Commit Acknowledgement Delay
•
Write Commit
•
Log Sent
•
Log Send Flow Buffer Wait
•
Log Sent From Cache
•
Send Queue
•
Roll Forward Queue
•
Log Received
•
Log Rolled Forward
•
Log Cache Redone
•
Log Harden Wait Time

Viewing the Role and Data Flow of the Selected Database

The Role and Data Flow of Database section displays the mirroring operation of the database selected in the Mirroring table and its mirroring partner. The monitored instance is always displayed on the left, and the data is shown as flowing in this instance’s direction, that is: Log Received if the database is Mirror, and Log Sent if the database is Principal.

Figure 25. The Role and Data Flow of Database displays the mirrored databases.

To investigate the data flow by displaying the selected database’s mirroring partner, use one of the following methods:

•
Click the cylinder icon that represents the mirroring partner
•
Click the link Investigate using the Partner’s Mirroring Page on the upper right side of the panel, above the table.

If the partner is currently monitored, its mirroring page will now be displayed. For details, see Viewing the Partner’s Mirroring Page . Otherwise, an error message is displayed, notifying that the partner server is currently not monitored.

Viewing the Selected Database's Mirroring Performance History

Viewing the Selected Database’s Mirroring Performance History

Clicking the Mirroring Role column of the Mirroring table displays the database’s Mirroring Performance History page, which allows carrying out the tasks described in the following sections:

•
Tracking the mirroring role over time
•
Tracking data transfer between the principal and the mirror databases
•
Tracking the mirroring roundtrip during the selected time range
Tracking the mirroring role over time

The Mirroring Role pane displays the role the database played in the mirroring operation during the selected time range: Principal, Mirror, or Not Mirroring.

The mirroring role is displayed as a gauge, with each of the mirroring roles indicated by another color. Positioning the cursor over the gauge displays the percentage, within the specified time range, the database spent in each role.

Tracking data transfer between the principal and the mirror databases

The middle section of the Mirroring Performance History page includes the following panes:

•
Principal Counters — this pane displays a chart of the following values, which can be selected from the list on the upper left:
•
Commit Acknowledgement Delay — indicates a delay in waiting for acknowledgement of unterminated transaction commit. This metric is specific to the principal database, and holds values only when a Full safety level is configured.
•
Write Commit — the number of transactions in the principal database that had to wait for a write commit in the mirror database's transaction log. Low values of this metric indicate a bottleneck.
•
Log Sent — indicates the rate, in megabytes, of log sent from the principal to the mirror database.
•
Log Send Flow Buffer Wait — the amount of time the mirroring session had to wait to use the mirroring flow control buffer. This value is specific to the principal database.
•
Log Sent from Cache — indicates the aggregated size, in megabytes, of the log records sent from the principal database cache rather than straight from the transaction log.
•
Send Queue — total size, in megabytes, of data waiting to be sent to the mirroring database.
•
Mirror Counters — this pane displays a chart of the following values, which can be selected from the list on the upper left:
•
Roll Forward Queue — total size, in megabytes, that remains to roll forward to the mirroring database.
•
Log Received — indicates the aggregated size, in megabytes, of log records received from the principal database.
•
Log Rolled Forward — the aggregated size, in megabytes, of log records that were rolled forward on the mirror database.
•
Log Cache Redone — the aggregated size, in megabytes, of log records that are being read from redo cache rather than from the transaction log. Constantly low values of this metric indicate that the transaction logs are arriving faster than they can be read by the redo task. This metric is specific to the mirror database.
•
Log Harden Wait Time — the amount of time spent waiting for the log to be written to the mirroring database. High values of this metric can indicate that the disk of the mirroring database is loaded.
Tracking the mirroring roundtrip during the selected time range

The Mirroring Roundtrip section displays a chart that indicates the latency of the mirroring session during the selected time range.

Viewing the Partner's Mirroring Page

Viewing the Partner’s Mirroring Page

When viewing the mirroring performance of a database that takes part in the mirroring operation, either as a principal or as a mirror database, it is possible to investigate the selected database’s mirroring partner, using one of the following methods:

•
Clicking the cylinder icon that represents the mirroring partner
•
Clicking the link Investigate using the Partner’s Mirroring Page on the upper right side of the table.

In so doing, the mirroring operation can be investigated from the point of view of the other database, thereby determining the source of the performance issue.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating