Foglight for SQL Server (Cartridge) 7.3.0


Display Name	Description
Available	0. Service is unavailable. 1. Service is available.
Up Since	Used to find how long the instance is up and running virtualization.
Working Set	Working Set is the current size, in bytes, of the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed, they will then be soft-faulted back into the Working Set before leaving main memory.
IOPs	Number of IO operations per minute.
% Processor	% CPU of SSIS Out of the entire CPU usage.
Bytes Read	The number of bytes read from all data sources in total.
Bytes Written	The number of bytes written to all data destinations in total.
Rows Read	The number of rows that a source produces in total. The number does not include rows read from reference tables by the Lookup transformation.
Rows Written	The number of rows offered to a destination in total. The number does not reflect rows written to the destination datastore.
Buffers Memory	The average amount of physical and virtual memory used by the data flow task.
Buffers Spooled	The total number of buffers written to disk during data flow tasks in the selected timeframe. Buffer is written to disk when the data flow engine runs low on physical memory.
Buffers In Use	The average number of buffer objects used by all data flow components and data flow engine during the selected timeframe.
Total Executions Count	The total number of packages execution in the examined era.
Failed Executions Count	The total number of failed packages.
Currently Running	The number of currently running packages.
Succeeded Execution Count	The number of successes packages run.
Others	Other packages running results.
Distinct Executed Packages	The number of distinct packages runs.
Current Number of Packages	The current number of packages.
Days Since Last Backup	Days since last backup.
Encryption Algorithm	The type of encryption algorithm that is used to encrypt sensitive data. The supported values include: DES, TRIPLE_DES, TRIPLE_DES_3KEY, DESX, AES_128, AES_192, and AES_256. NOTE: The catalog database must be in single-user mode in order to change this property.
Max Project Versions	The number of new project versions that are retained for a single project. When version cleanup is enabled, older versions beyond this count are deleted.
Operation Cleanup Enabled	When the value is TRUE, operation details and operation messages older than RETENTION_WINDOW (days) are deleted from the catalog. When the value is FALSE, all operation details and operation messages are stored in the catalog. NOTE: A SQL Server job performs the operation cleanup.
Retention Window	The number of days that operation details and operation messages are stored in the catalog. When the value is -1, the retention window is infinite. NOTE: If no cleanup is desired, set OPERATION_CLEANUP_ENABLED to FALSE.
Schema Build	The build number of the SSISDB catalog database schema. This number changes whenever the SSISDB catalog is created or upgraded.
Schema Version	The major version number of the SSISDB catalog database schema. This number changes whenever the SSISDB catalog is created or the major version is upgraded.
Server Logging Level	The default logging level for the Integration Services server.
Version Cleanup Enabled	When the value is TRUE, only the MAX_PROJECT_VERSIONS number of project versions are stored in the catalog and all other project versions are deleted. When the value is FALSE, all project versions are stored in the catalog. NOTE: A SQL Server job performs the operation cleanup.
Operation Log Number of Records	The number of total operations in the Integration Services catalog.
Operation Log Size	Total operation log size.
Version Log Number of Records	Total number of records in the log versions of objects in the Integration Services catalog.
Version Log Size	Total size of the objects versions log in the Integration Services catalog.

Statistics

Purpose

This collection provides a summary of SQL Server batches and compilations.

Type

System.

Collection Sampling Intervals


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

Collection Metrics


Display Name	Description
Batch Executions	SQL Batches being submitted to SQL Server for execution.
Batch Executions Rate	The rate per second at which SQL batches are being submitted to SQL Server for execution.
Compiles	Compiling is the process by which SQL Server converts the SQL statement into an executable query plan.
Compiles Rate	The rate per second at which SQL Statements are compiled, that is: converted into an executable query plan.
ReCompiles	A recompile occurs when SQL Server determines that the execution plan for a stored procedure that is currently executing may no longer be the best possible plan.
Redundant Compilations Ratio	Percentage of SQL recompilations that take place. A high percentage of SQL recompilations may indicate the need for additional physical memory. This ratio is calculated as follows: 100 * (Compiles / Compiles + Recompiles)

Top SQLs

Purpose

This collection collects data of SQL Statements that consumed the highest amount of resources during the specified time range.

Type

SQL Server.

Collection Sampling Intervals


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

Collection Metrics


Display Name	Description
Creation Date	Indicates the date the SQL statement was first run, thereby allowing the creation of SQL statement statistics
Diff. From Executions	Indicates the incremental difference in the number of SQL executions since the last sample.
Diff. From Total CLR Time	Indicates the incremental difference, since the last sample, in the total CLR time spent for executing the SQL statements.
Diff. From Total CPU	Indicates the incremental difference, since the last sample, in the total CPU time consumed by the SQL executions.
Diff. From Total Elapsed Time	Indicates the incremental difference, since the last sample, in the total time consumed for carrying out the SQL statement.
Diff. From Total I/O	The incremental difference, since the last sample, in the total number of I/O operations that were carried out for executing the SQL statements.
Diff. From Total Logical Reads	The incremental difference, since the last sample, in the total number of logical reads carried out for executing the SQL statements.
Diff. From Total Physical Reads	The incremental difference, since the last sample, in the total number of physical reads carried out upon executing SQL statements.
Diff. From Total Wait Time	The incremental difference, since the last sample, in the total wait time consumed upon executing SQL statements.
Executions	Indicates the number of times the SQL script executed for a unique SQL Handle.
Last Executed	Indicates the last time the SQL statement was executed (last run).
Plan Handle	Provides a unique identification of a SQL statement execution plan.
Query Hash	Query hash value indicates the logic behind a SQL script. Similar SQL queries (that is, SQL queries that differ by literal rather than logical values) have the same query hash value. Therefore, if the execution of such queries results in different query plan hash values, the reason for the difference is most probably the data against which the queries were executed.
SQL Handle	Provides a unique identification of a SQL batch script.
SQL Hit Rate	The percentage of SQL Statements that found the required plan already in the cache. If a matching plan is found, SQL Server does not need to compile the query or the stored procedure. This can save a significant amount of CPU resources, and speed up SQL Server queries.
Statement End Offset	A SQL batch may be combined of multiple SQL statements. While the SQL handle identifies the batch as a whole, this metric provides a unique identification of a specific SQL statement, by indicating the end position of the statement within the SQL batch.
Statement Start Offset	A SQL batch may be combined of multiple SQL statements. While the SQL handle identifies the batch as a whole, this metric provides a unique identification of a specific SQL statement, by indicating the start position of the statement within the SQL batch.
Total CLR Time	The total CLR time spent for executing the SQL statements.
Total CLR Time Per Exec	The average CLR time spent for executing a single CLR execution.
Total CLR Time Rate Top SQL	The total CLR time per second spent for executing the CLR execution.
Total CPU	The total CPU time consumed by the SQL executions.
Total CPU Per Exec	The average CPU time spent for executing a single SQL statement.
Total Elapsed Time	The total time consumed for carrying out the SQL statement executions.
Total Elapsed Time Per Exec	The average time spent for executing a single SQL statement.
Total I/O	The total number of I/O operations that were carried out for executing the SQL statements.
Total I/O per Exec	The average number of I/O operations carried out for executing a single SQL statement.
Total I/O Rate Top SQL	The total number of I/O operations per second that were carried out for executing the SQL statements.
Total Logical Reads	The total number of logical reads carried out for executing the SQL statements.
Total Logical Reads Per Exec	The average number of logical reads carried out for executing a single SQL statements.
Total Logical Reads Rate Top SQL	The total number of logical reads per second that were carried out for executing the SQL statements.
Total Physical Reads	The total number of physical reads carried out for executing the SQL statements.
Total Physical Reads Per Exec	The average number of physical reads carried out per execution of a single SQL statement.
Total Wait Time	The total wait time spent while executing the SQL statements.
Total Wait Time Per Exec	The average time spent on wait events while executing a single SQL statement.