Foglight for SQL Server (Cartridge) 5.9.4.20


Metric Display Name	Description
Connection Timeout	Defines the number of seconds that the principal database can be in Disconnected state, before the mirroring session will actually run a failover scenario to the mirroring database.
Database Name	The name of the database.
End Log LSN	The actual LSN (Log Sequence Number) of the mirroring session, This value should be equal to the Failover LSN value.
Failover LSN	The LSN (Log Sequence Number) value that the mirroring database should have in order to enable a smooth failover.
Mirror	The name of the instance whose role in the mirroring process is Mirror.
Mirroring Role	The role the database takes in the mirroring process; either principal or mirror.
Mirroring Status	Indicates the severity determined based on the database state: Normal, Warning or Critical.
Partner Name	The server network address defined for the Partner.
Principal	The name of the instance whose role in the mirroring process is Principal.
Redo Queue	The redo queue size. This size can be either lett Unlimited or defined in MB.
Replication LSN	The LSN (Log Sequence Number) used by the replication session (If such a session exists).
Role Sequence	A cumulative number that indicates the number of role switches that took place between the two partners involved in the mirroring process.
Safety Level	The safety level at which the mirroring session is configured to work (high availability /high performance).
Witness Name	The server network address defined for the Witness.
Witness State	The state of the Witness instance (valid only when the High Safety level is configured).

Mirroring Performance Counters

This collection retrieves data regarding performance and data flow-related issues between the databases involved in the mirroring operation.

Type

System.

Collection Sampling Intervals


Frequency Mode	Collection Interval (In Seconds)
Real-time	300
Online	300
Offline	900

Collection Metrics


Display Name	Description
Commit Acknowledgment 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.
Database Name	The name of the database.
Log Remaining For Undo	Indicates the size of transaction logs in the mirror database that remain for recovering the mirror database to its operative state. This metric holds data only after a failover has occurred.
Log Cache Redone	The amount of transaction log in MB that is being read from redo cache rather than from the transaction log. Constantly low values of this metric indicate that the transaction log is arriving faster than it 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. This value is specific to the mirror database.
Log Received	Indicates the rate in MB of log received from the principal database. This metric is specific to the mirror database.
Log Rolled Forward	The size in MB of log that was rolled forward on the mirror database. This value is specific to the mirror
Log Scanned For Undo	Indicates the size of transaction logs in the mirror database that were scanned for Undo. This metric holds data only after a failover has occurred, as the log scanning is carried out in order to restore the mirror database to its operative state.
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	Indicates the rate in MB of log sent from the principal to the mirror database. This metric is specific to the principal database.
Log Sent From Cache	Indicates the amount of log, in MB, sent from the principal database cache rather than straight from the transaction log. As sending from the cache is much faster and more efficient, this metric's values should be as high as possible. Constantly low values indicate that the transaction log generation rate is faster than the rate at which it is sent to the mirror database. This value is specific to the principal database.
Mirroring Roundtrip (Latency)	Indicates the latency of the mirroring session.
Occupied Cache Percent	The percentage of the occupied cache within the selected database.
Roll Forward Queue	Total size in MB that remains to roll forward to the mirroring database. This value is specific to the mirror database.
Send Queue	Total size in MB of data waiting to be sent to the mirroring database. This value is specific to the principal database.
Write Commit	This metric, which holds values only when a Full safety level is configured, indicates 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.

Missing Indexes

Collecting information about the indexes to be missing from each database.

Type

SQL Server.

Collection Sampling Intervals


Frequency Mode	Collection Interval (In Seconds)
Real-time	60
Online	60
Offline	3600

Collection Metrics


Display Name	Description
Database ID	The database ID where the missing index is located.
Database Name	The database name.
Schema Name	The schema name of the missing index.
Object ID	The object ID where the missing index is located.
Object Name	The object name the resource is part of.
Object Type	Type of object.
Is Ms Shipped	Object is created by an internal SQL Server component.
Create Date Utc	Date the object was created.
Modify Date Utc	Date the object was last modified by using an ALTER statement. If the object is a table or a view, modify_date also changes when a clustered index on the table or view is created or altered.
Index Group Handle	Identifies a missing index group.
Index Handle	Identifies a missing index that belongs to the group specified by index_group_handle.
Group Handle	Identifies a group of missing indexes. This identifier is unique across the server. The other columns provide information about all queries for which the index in the group is considered missing. An index group contains only one index.
Unique Compiles	Number of compilations and recompilations that would benefit from this missing index group. Compilations and recompilations of many different queries can contribute to this column value.
User Seeks	Number of seeks caused by user queries that the recommended index in the group could have been used for.
User Scans	Number of scans caused by user queries that the recommended index in the group could have been used for.
Last User Seek Utc	Date and time of last seek caused by user queries that the recommended index in the group could have been used for.
Last User Scan Utc	Date and time of last scan caused by user queries that the recommended index in the group could have been used for.
Average Total User Cost	Average cost of the user queries that could be reduced by the index in the group.
Average User Impact	Average percentage benefit that user queries could experience if this missing index group was implemented. The value means that the query cost would on average drop by this percentage if this missing index group was implemented.
System Seeks	Number of seeks caused by system queries, such as auto stats queries, that the recommended index in the group could have been used for.
System Scans	Number of scans caused by system queries that the recommended index in the group could have been used for.
Last System Seek Utc	Date and time of last system seek caused by system queries that the recommended index in the group could have been used for.
Last System Scan Utc	Date and time of last system scan caused by system queries that the recommended index in the group could have been used for.
Average Total System Cost	Average cost of the system queries that could be reduced by the index in the group.
Average System Impact	Average percentage benefit that system queries could experience if this missing index group was implemented. The value means that the query cost would on average drop by this percentage if this missing index group was implemented.
Equality Columns	Comma-separated list of columns that contribute to equality predicates of the form: table.column =constant_value
Inequality Columns	Comma-separated list of columns that contribute to inequality predicates, for example, predicates of the form: table.column > constant_value Any comparison operator other than "=" expresses inequality.
Included Columns	Comma-separated list of columns needed as covering columns for the query. For more information about covering or included columns, see Create Indexes with Included Columns. For memory-optimized indexes (both hash and memory-optimized nonclustered), ignore included_columns. All columns of the table are included in every memory-optimized index.

Plan Cache Distribution

Details the plan cache distribution, grouped by plan types and their use of related statistics.

Type

System.

Collection Sampling Intervals


Frequency Mode	Collection Interval (In Seconds)
Real-time	20
Online	60
Offline	300

Collection Metrics


Display Name	Description
Plan Cache Name	The types of objects that can appear in the Procedure Cache include: Trigger Plans: Query plans generated by creating a trigger. Replication Procedure Plans: Query plans of a replication system stored procedure. Procedure Plans: Query plans generated by creating a stored procedure. Prepared SQL Plans: Query plans corresponding to statements prepared via sp_prepare, sp_cursorprepare, or via auto-parameterized or user-parameterized queries. Misc. Normalized Trees: Normalized trees for views, rules, computed columns, and check constraints. Execution Contexts: Data structures that hold the data (such as parameter values) that is specific to the execution of user queries. Cursors: Extensions to result sets that provide the mechanism for working with individual rows, or a small block of rows, in a table. Ad Hoc SQL Plans: Query plans produced for an ad hoc query. Types of objects that can appear in the Procedure Cache for a SQL Server 2005 connection include: Bound Trees: Normalized trees for views, rules, computed columns, and check constraints. Extended Stored procedures: Catalog information for extended store procedures. Object plans: Query plans generated by creating a stored procedure, function, or trigger. SQL Plans: Query plans corresponding to statements prepared via sp_prepare, sp_cursorprepare, or via auto-parameterized or user-parameterized queries. Temporary Tables & Table Variables: Cache information related to temporary tables and table variables.
Cache Size	The amount of memory allocated to the procedure cache over time and breaks it down by object type.
Cache Hit Rate	The amount of memory allocated to the procedure cache over time and breaks it down by object type.
Cache Reads	Cache lookups.
Cache Hit Rate Percent	The percentage of compilations that are being saved by objects already in the procedure cache. The hit rate for this cache will vary widely depending on how your applications are written.
Object Count	The number of objects of each type that are currently in the procedure cache.
Use Count	The rate at which each type of procedure cache objects are being executed (used).

제품을 선택하십시오.

더 나은 서비스 제공을 위해 채팅 목적을 작성해 주십시오.

문제에 대한 권장 솔루션

Foglight for SQL Server (Cartridge) 5.9.4.20 - User Guide

Mirroring

Mirroring Performance Counters

Missing Indexes

Plan Cache Distribution