Chat now with support
Chat with Support

Foglight for SQL Server (Cartridge) - Release Notes

Issues also resolved in version and


Added ASP parameter to control maximum Host disk queue length and the default value of the parameter is 5000.


Fixed an issue that it might fail to execute the callback: [BLOCKING_LIST] and display error on blocking (current).


Fixed an issue where the users could not change the “Connect as” sysdba/normal in Migration Dashboard.


Fixed an issue that the agent might log exception when the backup location is a virtual disk.


Fixed an issue where it might fail to create SQL PI database when the initialize size is smaller than that of the Model database.


Fixed an issue after migrating the PI from Infobright to SQL Server-based repository the PI engine might be paused.


Fixed an issue when the agent name contains '[]', the Jobs list might not show up in Administration > Alarms > DBSS - Job Failed > Rule Exceptions.


Fixed an issue where Database dashboard might not be able to sort by the size column.


Fixed an issue where SQL - Disk Space Usage Report PDF might miss detail rows if file_groups.files.virtual_file_statistics has no data.


Fixed an issue where the collection colMaxRows value is set too small for customer's environment, and customer might not get full Databases dashboard.


Fixed the missing metrics for SQL Server: Up Since and Availability.


Fixed an issue where showplan parsing might be wrong for operation: Clustered Index Seek.


Fixed an issue where data in Local Last Backup Date field might be incorrect after all backup information has been deleted.


Fixed an issue where data for Disk Space might miss when having a snapshot in the instance.


Fixed an issue after clicking inactive session wrong dialog might pop up.


Fixed an issue when the system have hundreds of agents, the table records grow very fast. And 'registry_registry_value' and 'registry_registry_variable' take more than 1TB.


Fixed an issue where the Blocking (Current) page in SQL Server cartridge is very slow to load when the number of rows is >10.


Fixed an issue when the locale is GERMAN, the Workload summary report always displays 0.00% for each resource breakdown.


Fixed an issue when users access Manage SQL PI Repository from Databases dashboard, the FMS console might hang.


Fixed an issue where the dashboard I/O by File might not display a period value.


Fixed an issue where the DB agent log might print password information as Pa$$word, even if the value has been encrypted.


Fixed an issue where on-demand data connections might fail unless more TCP ports are opened.


Fixed an issue when configuring Rule exceptions for rule DBSS - Hours Since Last Log Backup, it might not work.


Fixed an issue when the customer have many system events files, the current deadlock query might consume high CPU, and the query execution time might need several minutes.


Fixed an issue when the percentage of usage exceeds 100, there might be gaps in SQL Server Memory > Summary > Memory Used graph.

Known issues

General issues



PI engine didn't use new credential changed in Connection Details dashboard.

Workaround: Reactive the agent after changing the credential.


Cannot use cluster server or AlwaysOn listener to monitor AlwaysOn environment on FIPS-enabled FMS.

Workaround: Refer to KB 324797 for detailed information.


When there are many DB agents with PI enabled in FMS environment and you want to upgrade the cartridge to the latest version, the SQL PI component update might fail.

Workaround: Click Cancel on Update SQL PI Failed and click Update SQL PI Components to update again.


DB instance is still synchronized and displayed in FMS federation master even though it is stopped for some reason and not displayed in the FMS federation child.


After DB agent restarts, there will be a 5 minutes data gap in the SQL PI baseline view.


Incomprehensible error message is displayed when using local account without hostname prefix to setup PI Repository.

Workaround: Use hostname\username to setup PI Repository instead of only using username.


Enabling SQL PI is only supported when the SQL PI agent manager is installed on one of the following operating systems:



“Context infos” display null in the Comparison Parameter dashboard.


An error log showed in FMS log for loading heatmap component in FMS version before 5.9.3.


If two SQL Server instances running in different hosts but these two hosts have the same short name, these two hosts shows same on the Home page.

Workaround: Contact Quest support to get the scripts for updating the loadGVData function.


Due to the metric collection interval, value of Data files, log files, and disk space metrics will be occasionally missing on the Databases > Temdb dashboard.

Workaround: Wait for 3 minutes, then you will see these metrics on the dashboard.


It fails to run DBSSSQLAgentErrorLogProcessor processor of DBSS_SQL_Agent_Error_Log collection if the SQL Server Agent Service is not started.

Workaround: Start the SQL Server Agent Service.


DBSS_Error_Log_List collection fails if SQL Server 2017 Agent is not running on Linux.


Logical Disk metrics of SUSE showing on the SQL Server Overview dashboard is different from its value showing in the Infrastructure dashboard.


Alarm is not triggered while the error has been collected on the DBSS - SQL Server Error Log page.


If AD authentication has been used to monitor SQL Server instance, the default option 'Log in to the host using the same account used for monitoring SQL Server' cannot be used to monitor Linux Operating System (OS).

Workaround: Switch to use the option 'Log in to the host using different login credentials', then choose either of the following Linux authentication types: input AD account info, input other Linux account info, or use 'Select from stored credentials...'.


When using IP address to create a SQL server agent, Disk metric and Host metric will be missing in the Global view.


Using CLI to create multiple SQL Server instances with OS monitoring might result in failure to activate some host agents.

Workaround: Either activate those host agents manually on the Agent Status dashboard or re-create those host agents.


When monitoring SQL Server 2017 on Linux, an error message will be shown in Logs > SQL Agent Error Logs page.


If you select either of DB_SQL_Server, DB_SQL_Server_UI, DB_Global_View_UI, SPIRepository* cartridges then click Reset on the Cartridge Inventory dashboard, the upgrade wizard will prompt again.

Workaround: Do the following:

Navigate to the Administration > Rules & Notifications > Manage Registry Variables dashboard.
Search for DBSS_Is_Fglams_Required_Upgrade.


Creating Infrastructure agent automatically after failover occurs on Linux-based SQL Server cluster may fail.


In the Master server of the federation environment, the values in Message of back up alarm are null.


When SQL Server cluster on Linux does fail-over, IC agent may not be auto created when the host name of the node is different with previous node.


Databases Replication Dashboard does not show all Subscriptions when using multiple distribution databases.


Failed to monitor SQL Server 2005 on premise while using no required permission DB credential.

Workaround: Download the DB_SQL_Server_Grant_Permission_Script from Components for Download, execute the script at SQL Server client to grant permission to the new user, then use the new user to monitor SQL Server 2005 Instance.


Databases on a secondary replica are read-only, so the grant script cannot create the user in the database. The Foglight user may still not be able to read data from these read-only replicas even if the users are synchronized.



When the VMwarePerformance Agent exists, the Disk Latency in SQL Server Overview would always show “-” while enabling OS monitoring.


On SQL Server 2008, deadlocks on two different databases of the same instance become one chained deadlock.

Workaround: Implement trace flag -T1234.


When working with Global View while the screen resolution is set to 1024 by 768 pixels, it is advisable to switch to the browser's full view (F11 toggles between full and normal views in all browsers).


User-defined collection names and fields must be entered in Latin characters (A to Z), without any special symbols.


The DBSS- Deadlock Details alarm is disabled by default.


Changes made in the Global Administrations > Alarms screen are saved when switching to another global administration screen, even if selecting “Yes” in the dialog box that asks whether to exit without saving changes.


Editing a user-defined collection results in periodic overlap of data.


Creating a user-defined collection with more than one SQL in it will not alert the user, however, only the first SQL in the collection will be executed.


When editing the properties of the Foglight Agent Manager concentrator (Dashboards > Administration > Agents > Agent Status), the name of the Foglight Agent Managers should be entered in the Downstream FglAMs section exactly as they appear in the topology, under Home > Agents > All agents > <Agent name> > RMI data > FglAM host property.

SSDB-8987, SSDB-7326

On Microsoft® Windows® 2008 R2, a SQL Server version 2012 instance with a name that contains inverted commas (''; (for example:'X641_ENT1') can encounter issues with the retrieval of WMI data. This is by design on the part of Microsoft.

Workaround: If WMI data is not retrieved, the instance name without the '' should be added in the field Service Name in the Agent Properties dashboard.


Cluster data can be collected only if the xp_cmdshell parameter is configured.

To configure this parameter, run the following commands:

EXEC sp_configure ‘show advanced options’,1


--To update the currently configured value for advanced options.



—- To enable the feature.

EXEC sp_configure ‘xp_cmdshell’, 1


—- To update the currently configured value for this feature.




In SQL Server® 2012, when a database is part of an availability group and is currently accessible for connections, when the application intent is set to read only, several collections will fail.


Selecting a batch text in the lock tree may navigate to a non-equal batch in the TSQL Batches dimension.


In environments configured to use Agent Manager in High Availability mode the chosen Agent Manager hosting the SQL PI repository will host watchdog and maintenance agents that cannot participate in the Agent Manager high availability utility.


The SQL Server Error log collection requires you to use WinShell. Follow the instructions below to configure the correct settings:


SQL BI - Reporting services, integration services and Analysis services are not supported on cluster configuration.


In case the privilege of OS monitoring is not set to the Local Administrator group on the host being monitored, see the Knowledge Article 215054.


Performing an upgrade process on a large environment (more than 50 agents) takes time to complete.


When running user-defined collections on dynamic tables, deleted items are still kept in the topology. As a result, the number of rows displayed on the user-defined collections table will exceed the configured value for maximum allowed rows.


In the Global Administration > User-defined Collections screen, it is possible to create two collections that bear the same name with a different capitalization (for example: MyCollection and Mycollection); however, the more recently created collection will not appear in the topology, nor will it be displayed on the User-defined Collections panel.


Need to wait for more than ten minutes between the upgrade of the Foglight Management Server and Foglight for SQL Server.


In environments configured to monitor SSAS agent only, when upgrading to version or later, the upgrade process will fail.

Workaround: In the Administration > Agents > Agent Status dashboard, click Deploy Agent Package, then follow on-screen instructions to deploy the SSAS package manually.


Monitoring Analysis services is supported only on Agent Managers running on Windows which must have a version of .NET 3.5 installed.


If the WMI exception “Format specifier '%s' “ is entered in agent log the following workaround is recommended:


For Windows® Vista® and Windows Server 2008 or above:

According to, the default dynamic port range for TCP/IP has changed in both versions. The new default start port is 49152 and end port is 65535. Subsequently, monitoring instances that run under these operating systems can be carried out by setting a static (fixed) WMI port in Windows Server.

For more information, see the Knowledge Article 114559.


When Foglight or the Agent Manager are installed on a VM, it is highly recommended to reserve the following:

CPU - for a virtual machine the CPU reservation is highly recommended for better performance. The reservation is expressed in MHz.
RAM- for a virtual machine the memory reservation is highly recommended for better performance.


Antivirus exclusions is required for the SQL Server-based SQL PI repository. For more information refer to the Microsoft’s official article

Execution plan


Execution plan may not be resolved.


Sometimes, query_hash is changed by SQL Server and generating a plan using the Generate button fails. SQLhash isn't found in XML so the screen displays No operation was found and the execution plan changes are missing.


Time range changes are not affecting the execution plan dashboard.


In the Execution Plan comparison popup, the date of the selected plan is the insert time to the SQL PI repository and not the execution time.


In the Execution Plan Comparison popup for statement - the estimated plan appears only as the selected plan on the left side. It cannot be selected from the list.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating