Chat now with support
Chat with Support

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

Adding instances manually

To add instances manually:
1
Click Add instances.
2
Click Add manually.
The Add New SQL Server Instance dialog box appears.
3
Use this dialog box to enter the following details:
•
Server name — the SQL Server instance name. For default instance, specify the host name; for named instance, use the format: host name\instance name.
•
Port — Required for a SQL Server instance whose TCP/IP connection port is other than the default port (1433).
 
* 
IMPORTANT: If no port is specified, the wizard uses the port provided by the SQL Browser service (dynamic port), in which case this service must be started. After the instance monitoring configuration is complete, instances whose port was provided by the SQL Browser service have the number 0 displayed in their Port row.
4
Click Finish.
The newly added instance now appears on the table, with the status Set credentials.
5
Proceed with the wizard, starting from Step 5.

Discovering instances by host name

Searching by host is the most efficient search method for discovering instances over a specified, small number of hosts.

To search by host:
1
Click Add instances.
2
The Discover SQL Server Instances by Hosts dialog box appears.Type the host names in the field below the first check box. To specify multiple host names, separate the values by comma.
 
* 
IMPORTANT: Ensure typing host names and not IP addresses. IP addresses are supported only when searching by IP range, as detailed in section .
Alternatively, if Foglight already monitors one or more hosts in the selected environment, select the requested host from the table of hosts currently known to Foglight.
 
* 
IMPORTANT: The table lists all the hosts known to Foglight, regardless of the cartridge type, and including virtual hosts if the VMware cartridge is installed and configured.
3
Click Discover.
At the end of this process a table appears, displaying the newly discovered instances within the selected hosts.
4
Select the instances to be monitored.
5
Click Finish.
The newly added instance now appears on the table, with the status Set credentials.
6
Proceed with the wizard, starting from Step 5.

Discovering instances by IP range

Searching by IP range is the recommended search method for discovering database instances over many hosts, by that means saving the need to specify the host names and ports.

To search by IP range:
1
Click Add instances.
2
Click Discover by IP.
The dialog box Discover SQL Server Instance by IP Range appears.
The IP range displayed by default is determined by the IP address and the subnet mask on the selected Foglight server.
3
In the From box, type the IP Range.
 
* 
IMPORTANT: Ensure that the numbers entered are within the range of 0 to 255.
4
In the To box, type the requested IP Range.
 
* 
IMPORTANT: Ensure that the numbers entered are greater than those entered in the From box, and that the address range does not exceed 1000 addresses.
5
Click Discover.
At the end of this process a table appears, displaying the newly discovered instances within the selected hosts.
6
Select the instances to be monitored.
7
Click Finish.
The newly added instance now appears on the table, with the status Set credentials.
8
Proceed with the wizard, starting from Step 5.

Importing Instances from a File

Foglight for SQL Server supports importing an unlimited number of existing SQL Server instances that need to be monitored, using a predefined Regserv file that includes the properties of these instances.

* 
IMPORTANT: The Regserv file can also be created by exporting the list of registered servers in SQL Server Management Studio. To do that follow the instructions at: https://msdn.microsoft.com/en-us/library/ms190246.aspx
To import the '<NAME>.regsrvr' file:
1
Select the Import from file option.
2
Import the <NAME>.regsrvr file
3
The instances listed in the file is presented in the SQL Instances list.
4
Select the instance you want to monitor and proceed with the validation step.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating