サポートと今すぐチャット
サポートとのチャット

Foglight for SQL Server (Cartridge) 5.9.3.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 pull 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

Viewing Historical Metrics

The History section view is divided into two sections that are correlated to each other:

Selecting each dimension in the performance tree together with a specific resource effects the data displayed for each Level.

For example, by selecting the Lock resource the Instance view dimension will present only locks related data, the SQL Statements dimension will present only the statements that were experiencing locks and DB users the were experiencing locks and so on through all the dimensions and resources.

Resource Toolbar Options

 

The Workload resource is selected by default

The CPU panel allows you to review the CPU usage and CPU wait events.

The I/O panel allows you to review the I/O-related data, such as wait events and physical reads and writes.

Default metrics displayed:

The Memory panel allows you to view memory related performance data, such as wait events and physical reads and writes.

Default metrics displayed:

The Network panel displays the network related wait events.

Default metrics displayed:

The Lock panel displays the database’s lock related wait events.

Default metrics displayed:

The Latch panel displays the database’s latch related waited events.

Default metrics displayed:

The Log panel displays the database’s log related wait events.

Default metrics displayed:

The CLR panel displays the database’s wait events occurring as a result of statements waiting for CLR code execution to complete.

Default metric displayed:

The Remote Provider panel displays the databases wait events that take place when various processes are waiting either for a remote OLEDB call to complete or for DTS synchronization.

Default metrics displayed:

The Other panel allows monitoring the time spent waiting for the completion of miscellaneous operations. That is, operations that cannot be classified into any other wait categories.

Default metrics displayed:

 

The XTP pane displays information gathered by SQL Performance Investigator and XTP-related DVMVs. Metrics displayed are:

XTP Transaction Wait

Time spent waiting for in memory transaction events.

XTP Wait

Time spent waiting for in memory OLTP (XTP) related events.

XTP Miscellaneous Wait

Time spent waiting for in memory miscenllaneous events. Those events are not related to transactions, log or natively compiled stored procedures.

XTP Log write Wait

Time spent waiting for in memory log and checkpoint related events.

XTP Procedure Wait

Time spent waiting for events related to natively compiled stored procedures.

XTP Transactions

The total number of transactions that have run in the In Memory OLTP database engine.

XTP Failed due to Unique Contraint

Total number of unique constraint violations.

XTP Writes

Total number of megabytes written to the In Memory OLTP log records.

XTP Failed due to Write Conflicts

The number of conflicts between transactions while writing a row which lead to aborts.

XTP Transactions on Durable Tables

Total number of transactions that require log IO. Only considers transactions on durable tables.

XTP Failed due to Dependencies

The number of times a transaction aborts because a transaction on which it was dependent aborts.

XTP Read Only Transactions

The number of read only transactions.

XTP Failed due to Validation

The number of times a transaction has aborted due to a validation failure.

XTP Aborted Transactions

The total number of transactions that were aborted, either through user or system abort.

In general, the XTP option on the SQL performance dashboard should show none or almost none XTP wait consumption. The most likely way to observe any XTP activity would be to show background processes.

However, in case there are significant waits related to XTP activity; use the Resource Breakdown pie chart. Clicking on the "All Wait Events" anchor allows you to get the actual wait counts. This drilldown display also allows you to compare the XTP wait events in comparison with other waits detected by SQL PI.

Use the XTP related Metrics:

These metrics allow you to find if there were XTP transactions that failed. They also enable research on the top reasons of failure. Clicking on each of these values allows you to investigate the amount of failure over time.

Viewing Change Tracking

The change tracking tool is an integrated monitoring mechanism. It periodically tracks changes in environments and activity that can potentially influence system performance and enables the user to view correlation between occurrences of changes and SQL Server's activity and behavior patterns.

Use the Categories filter mechanism to refine the set of displayed change tracking occurrences. These categories are displayed on the right hand side of the pane and include:

For each database in an MSSQL instance: Users and permissions changes.

For each database in an MSSQL instance: File group parameters; files (data, log and control) location, size and status.

For each database in an MSSQL instance: Any schema object: Tables and indexes and their partitions and sub-partitions; clustered and non-clustered indexes; constraints; views; functions; procedures; types and triggers (for example, altering a table; altering or rebuilding an index).

SQL PI captures SQL statements whose execution plans have changed. When an execution plan has (unintentionally) changed, the outcome can result in SQL performance degradation. Therefore it is essential you investigate the change, by clicking the Properties button to graphically display the execution plan before and after the change, to verify that the nature and outcome of the change improve SQL performance.

Master database: file groups, files, instance configuration, and databases defined in the instance. The master database houses all critical information such as server specific configuration information, user login accounts, running processes, system error messages, system stored procedures, and the location of the primary files that contain the initialization information for the user databases.

Hardware and operating system configuration (for example, disks and network interfaces (NIC); amount of RAM; CPU count; device installations and swap space allocation).

Viewing Execution Plans

This view presents the execution plan of a selected SQL\batch and the cost of it. A Historical execution plan can be generated and will present any two views of the execution plan.

There are two ways to access the Execution Plan History dialog:

The execution plan dashboard displays the following content.

Date — Displays all the execution date and time of the selected statement\batch

Type — Displays the type of the execution plan.

Plan handle — Displays the SQL handle on the execution plan.

The execution plan is displayed in tabs which present the cost of each operation and object of each step of the plan.

By pressing the Generate Plan button the execution plan is generated and can be viewed by clicking on Compare Plan. This opens a pop up with a compression of all available execution plans of the selected statement.

Provides the same view as without SQL PI configured. See Blocking History .

Provides the same view as without SQL PI configured. See Viewing SQL Statement Details .

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択