Chatta subito con l'assistenza
Chat con il supporto

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

Monitoring Full-text Indexes using the Full Text Search Panel

In full-text indexing, a separate catalog is maintained that indexes each word in a database field as a separate index entry. The Full Text Search panel displays performance details for all full-text indexes on the server.

To create a custom filter for this table, use the options accessible by clicking Advanced. For details, see Components Shared by all Foglight for SQL Server Screens .

 
Table 54. The Full Text Search Service table contains the following data.
Data Series
Description
Database Name

The name of the database where the tables in the Full Text Catalog reside. Provides a unique identification of the database within a SQL Server instance.

ID

ID of the full-text catalog. Provides a unique identification across the full-text catalogs in the database.

FTC Name

The name of the full-text catalog. Provides a unique identification within the database.

Status

The status of the full-text catalog. Can have one of the following values:

•
0 — Idle
•
1 — Full population in progress
•
2 — Paused
•
3 — Throttled
•
4 — Recovering
•
5 — Shutdown
•
6 — Incremental population in progress
•
7 — Building index
•
8 — Disk is full. Paused.
•
9 — Change tracking
Index Size MB

The size of the full-text index, in megabytes, rounded to the nearest value.

Item Count

The number of items currently found in the full-text catalog.

Path

The name of the catalog directory in the file system.

Last Populated

Displays the time when the full text index was last populated; returns 0 if no population has occurred.

Table Count

The number of tables in the database that take part in the full text indexing process.

Using the HADR Drilldown

The HADR drilldown provides monitoring information regarding the disaster recovering solutions provided by SQL Server: Log Shipping, Cluster, Mirroring, and Always On.

While the data in the Log Shipping panel is available for all versions of SQL Server:

•
The Cluster panel data is only available for instances running on a cluster server that is installed on Windows platform.
•
The Mirroring panel data is only available for instances that are running on Windows platform and have databases configured for database mirroring.
•
The Always On panel requires a SQL Server version equipped with the Always On capability (SQL Server 2012 and higher).

Monitoring the Log Shipping

Log shipping is used for setting up backup databases to take the place of a current “live” database if that database goes down. To that end, database logs that are dumped on the live database are copied to the backup server and restored on the backup database.

Monitoring log shipping requires connecting to a monitor server (which may be the live server, one of its backups, or an outside monitor that does not take place in the log shipping process). The monitoring server is used for analyzing log shipping performance.

Foglight for SQL Server monitors log shipping for the following types of errors:

•
Backup threshold exceeded — the failure to back up a database log within a set period of time.
•
Out of Sync threshold exceeded — the failure to restore a database log to a backup server within a set period of time after the log has been backed up.
For details, see Log Shipping Alarm .

The Log Shipping panel allows investigating the cause for a log shipping alarm by carrying out the tasks detailed in the following topics:

•
Tracking the Performance of Servers used in Log Shipping
•
Viewing the Log Shipping Details .

Tracking the Performance of Servers used in Log Shipping

The Log Shipping table contains performance details for the primary and backup servers used in Log Shipping, as presented in the table below.

To create a custom filter for this table, use the options accessible by clicking Advanced. For details, see Components Shared by all Foglight for SQL Server Screens .

 
Table 55. The Log Shipping table contains performance details.
Column
Description
Server

The server name (Primary server for the parent instance, and Secondary server for all subsequent child instances).

DBName 

Depending on the instance role:

•
For the primary instance, the backup database on the source server
•
For the secondary instance, the destination database on the secondary server
Last Activity

Depending on the instance role:

•
For the primary instance, the last time the database was backed up
•
For the secondary instance, the last time a file was copied or restored
Activity Type

What activity was performed at the Last Activity time (Backup or Copy).

Threshold

The maximum allowed time (in minutes) before a Log Shipping alert occurs.

The amount of time depends on the instance role:

•
For the primary instance, this is the maximum allowed time since the last transaction log backup was made on the source server.
•
For the secondary instance — the maximum allowed time between the last backup on the source server and the last restore on the secondary server.
Outage

During an outage, no alerts occur when thresholds are exceeded (for both the parent and child instances). If this field is blank, no outage takes place.

Threshold Alert

The Error Log drilldown displays this alert if the threshold is exceeded.

Alert Enabled

If this option is selected, only enabled alerts are displayed.

 
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione