Chat now with support
Chat with Support

Foglight for SQL Server (Cartridge) - Release Notes

Resolved issues and enhancements

Resolved issues and enhancements

The following is a list of issues addressed and enhancements implemented in this release. 

Defect ID

Resolved Issue


It displays wrong sorting order when sorting by column "Up Since" in the Global View table.


Global View displays no data under some circumstances.


It encounters slow response of dashboards due to too many DB2 debug logs generated.


"Databases - SQL PI" dashboard sometimes displays blank in the federation master of Foglight server.


It sometimes raises a false alarm of "Unavailable SSAS service" when using SSAS agent to monitor SSAS cluster environment.


Add new sub wait categories to map new wait events from SQL Server 2017.


Set the Activity Highlights as the default tab in SQL PI.


It contains garbled characters in the SQL text when clicking Tune SQL button.


Change the type name of the execution plan in SQL PI for SQL Server.


Increase the socket timeout value to avoid frequent failure of SSAS agent creation.


Enhance the upgrade mechanism for PI repository to eliminate the unnecessary installation of Infobright software.


Enhance the deadlock trace with extended events for SQL Server versions greater than 2008.


The alarm "DBSS - Excessive Memory Pressure" is triggered falsely under some circumstances.


The Local User name in the "Operating System Monitoring Extension" dialog doesn't change accordingly when agent manager is switched in the Agent Setup wizard.


Data files stored in symbolic link drivers are not calculated for alarms "File Group Utilization".

SSFOG-921, SSFOG-922, SSFOG-965

Add a new field of agent creation to determine whether TLS v1.2 is used or not.


Enhance the alarm message for the alarm "SSRS - Reporting Services - Reports Failed Summary".


Enhance worker threads collection to query the number of active threads and maximum threads count.


Enhance the alarm message of the alarm "Jobs Failed" to include the job failure reason.


Alarm message for "DBSS - Days Since Last Backup" displays the Day value, which is less than the predefined threshold.


Top SQL Batch report only displays partial script of T-SQL Batch.


Tempdb > Sessions dashboard displays wrong metric names and misses an important metric.


It raises false alarm of "DBSS - Replication Publications - Status" when the status is null.


Add a new entry in ASP setting for the collection "Index Fragment Report" to allow the user to customize the time-out value.

Issues also resolved in version

Issues also resolved in version

The following is a list of issues addressed and enhancements implemented in release.

Defect ID

Resolved Issue


Unable to detect Agent Manager OS type and version when installing Infobright PI repository.


Lots of “dataprocessor.exe” processes get hung over time on Agent Manager and it causes the PI data submission failure.


Unable to enable PI when monitor Oracle instance as a sysdba user.


"NullPointerException" Error is thrown in the log when executing "Logical Disk Collection" in Windows environment which has dynamic disks and volumes.


Instance Availability displays n/a on SSIS Overview when SQL Server 2016 or later version is being monitored.


Unable to enable OS monitoring with "Local User" Authentication type when setting up SQL Server DB agents by CLI.


Unable to enable OS monitoring with "SSH (login credentials)" Authentication type when setting up SQL Server DB agents by CLI.


Unable to get correct session ID when "parent_connection_id" is null.


The error message showed up on User Level Access page after adding a new user.

Known issues

Known issues

The following is a list of issues known to exist at the time of this release.

General Issues

Defect ID

Known Issue


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.


When using SSAS agent to monitor SSAS cluster environment, "Unavailable SSAS service" alert may show up even the SSAS service is actually up.


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


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.


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


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


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:

1. Navigate to the Administration > Rules & Notifications > Manage Registry Variables dashboard.

2. Search for "DBSS_Is_Fglams_Required_Upgrade".

3. Change its value to "-1".


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 using IP address to create a SQL server agent, Disk metric and Host metric will be missing in the Global view.


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...'.


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


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


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.


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.


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.


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 available at


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


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


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.


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


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.


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.

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.


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.


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.


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


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.


The DBSS- Deadlock Details alarm is disabled by default.


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


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).


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

Workaround: Implement trace flag -T1234


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.


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.


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


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.


On mixed Windows and Linux environments, SQL PI stops monitoring after upgrading the Foglight database cartridge to and higher.

Workaround: Perform the procedure described in the Knowledge Article 212566. If you are upgrading from (and higher) to version or later, redo this procedure.


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 available at


In cases when Foglight or the Agent Manager are installed on a VM the following need to be reserved:

  • Memory - the full amount of the required machine memory

  • CPU - the amount of CPU MHz

Execution Plan

Defect ID

Known Issue


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 effecting 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.



Third party known issues

The following is a list of third party issues known to exist at the time of this release.


Defect ID

Known Issue


The Foglight Agent Manager (FglAM) failed to restart when upgrading DB Cartridge, which is due to "Could not obtain a deployment lock" error.

Workaround: Perform the procedure described in the Knowledge Article 266110.


Anti-Virus Protection tools installed on Windows® may negatively impact CPU and system performance of machines running Foglight the Agent Manager and the SQL PI repository.
To reduce resource consumption it is highly recommended that you exclude the following directories from being scanned by the Anti-Virus tools:

  • <installation directory>:\Quest\<foglight>

  • <installation directory>:\Infobright

  • <installation directory>:\Quest\<FoglightAgentManager>


WMI-related issue

Problem: WMI support is affected by the firewall

Workaround: For Windows versions prior to Windows 2008/Vista, use the following steps:

  1. Open TCP port: 135.
    WMI by default uses the port range 1024 to 5000.

  2. Open up a range of ports above port 5000.
    Port numbers below 5000 may already be in use by other applications and could cause conflicts with your DCOM applications. It is recommended to have at least 100 ports opened, as several system services rely on these RPC ports to communicate with each other.

  3. Add the registry key, including additional ports.

    • Use the RPCCfg.exe (Windows Resource Kits) by running: rpccfg.exe -pe 5009-5009 -d 0

    • Manually add the registry keys under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet

For Windows Vista® and Windows Server 2008:

According to Microsoft®, the default dynamic port range for TCP/IP has changed in these versions. The new default start port is 49152 and end port is 65535.

Subsequently, monitoring instances that run under these operation systems can be carried out by using either of the following options:

  • Configure the firewalls to allow traffic between servers in the dynamic port range of 49152 through 65535 (less secure).

  • Limit the port range that is used in each monitored server.


As a result of the change introduced in Java 6 update 29 to how data is sent to databases, users may experience connection failures when using the Microsoft JDBC Driver for SQL Server® to connect to SQL Server. This interoperability enhancement is available in the following SQL Server versions:

  • SQL Server 2012 Production version and later

  • SQL Server 2008 Service Pack 3 Cumulative Update 4

  • SQL Server 2008R2 Service Pack 1 Cumulative Update 6

  • SQL Server 2008R2 Service Pack 2


Third Party Limitations

Monitoring an SQL Server instance that resides on a Windows 2008R2 or higher requires a workaround as follows:

  1. Browse to and log in

  2. Perform solution


Some base values are not updated when using the Win32_PerfRawData_PerfDisk_LogicalDisk WMI class to calculate performance data in Windows Vista or in Windows Server 2008, because this class does not contain the PercentDiskTime_Base metric.

Workaround: A hotfix is available on Microsoft site,


Due to a known Microsoft issue (, on SQL Server instances version 2014 the SQL text presented may be truncated.


The Windows System Center 2012 Endpoint Protection tool may negatively impact CPU and system performance of machines running Foglight and the Agent Manager. To reduce resource consumption it is highly recommended that you exclude the following directories from being scanned by the tool:

  • <installation directory>\Quest\<foglight>

  • <installation directory>\Infobright

  • <installation directory>\Quest\<FoglightAgentManager>


SQL's and execution plans may not be collected on SQL Server 2014 as a result of a Microsoft bug

"The values of column query_hash and query_plan_hash are NULL for DMV sys.dm_exec_requests in SQL Server 2014"


The Foglight Time Bar Chart click event does not work with Chrome version 40.x.x.x and 39.x.x.x.


Workaround for all missing WMI metric cases

In some cases, running the command: %windir%\system32\wbem\wmiadap.exe /f in Windows' command-line (CMD) may solve the problem of missing WMI classes. This command parses all the performance libraries on the system and refreshes the Performance Counter Classes. For further details, see


Upgrade and compatibility

Upgrade and compatibility

A direct upgrade to Foglight For SQL Server is only available from version 5.7.5.x or above. Customers that are running 5.7.x of the product must first upgrade to version 5.7.5.x and then upgrade to version A direct upgrade to Foglight for SQL Server 5.7.x is only available from version 5.5.8 or later. Customers that are running earlier versions of the product must first upgrade to version 5.5.8 and then upgrade to version 5.7.x.

For example, if your Foglight for SQL Server is version 5.5.8 and you are going to upgrade to version, the upgrade path will be 5.5.8 > 5.7.x > 5.7.5.x (or above) >


Foglight for SQL Server requires:

  • Management Server version 5.9.2, 5.9.3, or 5.9.4
  • Agent Manager version 5.9.2, 5.9.3, or 5.9.4

To upgrade Foglight for SQL Server:

  • Install version of the cartridge as you would install a new Foglight for SQL Server cartridge. Do not delete the older version of the .car file. Install version over the older version.
    For cartridge installation instructions, see the Foglight for Databases Deployment Guide.

Once you have upgraded the cartridge, to deploy the agent package, navigate to the Global View dashboard and follow the upgrade wizard instructions. For a procedure describing how to deploy the agent package, see the Foglight for Databases Deployment Guide.

Note: Foglight for SQL Server does not support the upgrade method of placing the new version in the folder <foglight_home>/upgrade/cartridge/.

Important: If you are upgrading to the current version of Foglight for SQL Server in a Federation architecture, the upgrade should be applied first to the Federated Children and then to the Federation Master. If the Federation Master is upgraded first, it will display incorrect information regarding the number of instances being monitored in the Status Summary section.


The following Foglight product versions and platforms are compatible with this release.

Product Name

Product Version


Foglight Management Server




All platforms supported by these versions of the Foglight Management Server

Foglight Agent Manager

Note: The monitoring agents available in this version of Foglight for SQL Server support the Agent Manager HA failover mode, except for the Agent Manager monitoring SQL PI agents. For more information about this mode, see the Agent Manager Guide.




All platforms supported by these versions of the Foglight Agent Manager


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating