Foglight™ for SQL Server

Developed for Foglight Management Server 5.7.0

Release Notes

September 2017


Welcome to Foglight for SQL Server

New in this release

Resolved issues and enhancements

Known issues

Third party known issues

Upgrade and compatibility

System requirements


Product licensing

Getting started with Foglight for SQL Server

About Us


Welcome to Foglight for SQL Server

Foglight™ for SQL Server allows DBAs to quickly and efficiently identify performance deviations, determine their root cause, perform comprehensive analyses, and resolve performance bottlenecks. The product provides web-enabled dashboards for centralized visibility, management and health checks for the SQL Server® instances deployed in your environment, as well as proactive alerting and alarm workflows for tracking your responses to critical performance anomalies.

Foglight for SQL Server is an n-tier application, which leverages a web-based user interface to ensure having complete visibility into the SQL Server infrastructure wherever an Internet connection is available.


These Release Notes cover the resolved issues, known issues, workarounds and other important information about release of Foglight for SQL Server. Review all sections before starting installation. 


New in this release

Version contains the following new features and updates:


Resolved issues and enhancements

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

Defect ID

Resolved Issue


Fixed issue where some dashboards, copyright, and URL addresses have not been rebrand to Quest Software Inc.


Fixed issue where DB Groups Grid in the DB Global View could not be restored after disabling or upgrading the previous Global View cartridge.


Updated the Supported Foglight Version number on the Databases > Administration dashboard.


Out of Memory occurred when clicking an instance to access the Overview dashboard.


The "An error has occurred. Please check your logs." error showed on the Databases > Overview dashboard.


Clicking Version\Collation on the Overview dashboard leads to the previous Real Time page.


SQL PI Statistics debug messages were disabled by default.


Fixed issue where the Up_since metric could not be synchronized from FMS Child to FMS Master.


Removed the Time Range settings from the Set Input Parameters step for Index Fragmentation Report.


Failed to add Reporting Services using a custom ReportServer name.


The "Callback failure: no result received from callback" error was randomly occurred when setting up DB agent the first time.


Fixed issue where there was no databases popped up in the Specify Databases for Exclusion dialog box.


Fixed issue where inconsistency was occurred between disk latency metric and graph on SQL Server instance overview.


Removed redundant permission file from the Management Server module.


Fixed the performance issue occurred when importing a large number of AD groups into the Management Server


Excluding database moves all databases that contain the name of database being selected.


An error was occurred on the Alarms > Settings dashboard if the agent name contains slash.


Fixed issue where systemID collection was disabled by the IC agent created using the DB wizard.


DBSS - Long Running Job alarm will not be triggered on SQL Server 2008.


The "Failed to invoke agent callback" error prompted when setting up the SQL Server Agent.


Fixed issue where EXECUTE permission was denied on the object 'agent_datetime'.


Known issues

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

General Issues

Defect ID

Known Issue


The Timeout error occurs when enabling OS monitoring in the Management Server 5.7.1.

Workaround: Upgrade the Management Server to 5.7.5 or later.


The following metrics are missing on the Databases > Temdb dashboard: data files, log files, and disk space.


Anti virus applications block the SPM installer.


History data is missing if user upgrades the Foglight for SQL Server cartridge using the SPM installer.


PI extension cannot be enabled for DB agents that are deployed on mixed environments (Linux® and Windows®).

Workaround: Use the same version of DLP for both Linux and Windows environments. See the Knowledge Article 215534 for details.


DB agents need be re-upgraded after upgrading the Foglight Management Server.

Workaround: Make sure to wait for more than 10 minutes between upgrade of the Foglight Management Server and Foglight for SQL Server.


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


When PI is enabled, Microsoft Visual C++ 2010 Redistributable Package needs to be installed on Foglight Management Server and Foglight Agent Manager. It can be downloaded from here:


In case of mixed environments (Linux® and Windows®), upgrading Foglight for SQL Server to the latest version causes the agent monitored by SQL PI with SQL PI repository on Linux to stop monitoring.


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


If the WMI exception "Format specifier '%s' " is entered in agent log the following workarounds are recommended:


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


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


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.


A Foglight Agent Manager (FglAM) residing on a Linux/UNIX machine cannot use Windows Remote Management (WinRM) to establish a connection with a Windows server. Connection using WinRM can only be carried out by a Foglight Agent Manager (FglAM) residing on a Windows machine.


In an environment that includes a Foglight Agent Manager concentrator, when upgrading the environment where the concentrator does not contain any regular agents, the concentrator is not upgraded. Therefore, after the upgrade process takes place the Foglight Agent Manager concentrator has to be deployed manually.


When running the agent installation wizard on a monitored host whose OS version is Windows 2008 R2, the OS validation fails.

Workaround: review the following knowledge base article:

SSDB-7241, WCF-12907

Currently users can create a recursive service, which calls itself and thereby causes an endless loop. If a user creates such a service the Databases dashboard will not be displayed.


Reuse and copy of user-defined collections is only possible for collections that were created after the 5.6.4 version of the product was installed.


The reports wizard contains multiple "all reports" tabs. Each tab is for a different database type.


In a Federation environment, deleted agents are still displayed in the Global View > Databases  table.


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


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.


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.


row_count metric is supported from SQL Server version 10.50.2500 and above

Execution Plan

Defect ID

Known Issue


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.


Execution plan may not be resolved


Time range changes are not effecting the execution plan dashboard.


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.


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.



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


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>:\Dell\<foglight>

  • <installation directory>:\Infobright

  • <installation directory>:\Dell\<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 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:

  • c:\Dell\<foglight>
  • c:\Infobright
  • c:\Dell\<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

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.

Note: The Foglight for Infrastructure agent will not be created in the following scenarios:


Foglight for SQL Server requires Management Server version 5.7.0 or later and Agent Manager version 5.8.0 or later.

To upgrade Foglight for SQL Server:

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

5.7.0 or later

All platforms supported by this version 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.

5.8.0 or later

All platforms supported by this version of the Foglight Agent Manager


System requirements

Before installing Foglight for SQL Server, ensure that your system meets the hardware and software requirements detailed in Foglight System Requirements and Platform Support Guide. Customers running large deployments (more than 50 instances) should consult the Foglight for Databases Deployment Guide.

Supported Platforms for Monitoring



Operating System/
SQL Server Version

SQL Server 2000

SQL Server 2005

SQL Server 2008

SQL Server 2008 R2

SQL Server 2012

SQL Server 2014

SQL Server 2016









Windows Server® 2003








Windows Server 2008
















Windows Server 2003








Windows Server 2008








Windows Server 2008 R2








Windows Server 2012








Windows Server 2012 R2








Windows® 7








Windows 8 and 8.1








Windows 10





Require SP2 of SQL Server 2012, SQL PI

Require SP1 of SQL Server 2014, SQL PI





Final Browser Support Notice

Support for Microsoft® Internet Explorer® 8, 9, and 10 will be discontinued as of the next Foglight release.

Microsoft ended the support for these browsers on January 12, 2016. For more information, visit

These versions of Internet Explorer are supported in this release, as documented in the Foglight System Requirements and Platform Support Guide.



This section provides a list of references which address the most commonly faced issues relating to remote connectivity, allowing for easy troubleshooting using the vendor's information knowledgebase:


Product licensing

Foglight includes a licensing capability that restricts access to those features that are defined in the license. Any Management Server installation requires a license that grants access to server-specific parts of the browser interface and the features associated with them. Foglight cartridges are also license-protected. While some cartridges are covered by the base Foglight license (such as Foglight Agent Manager cartridges and the Foglight for Infrastructure), others may require an additional license.

Foglight for SQL Server is covered by the base Foglight license that allows cartridges to be installed. The SQL Performance Investigator extension requires a dedicated license.

To activate a trial or a purchased commercial license:

  1. On the navigation panel, under Dashboards, click Administration > Setup & Support > Manage Licenses.
  2. Click Install.
  3. In the Install License dialog box, click Browse.
  4. In the file browser that appears, specify the location of the license file.
  5. In the Install License dialog box, click Install License.


Getting started with Foglight for SQL Server

Contents of the release package

The Foglight for SQL Server release package contains the following:

  1. Foglight for SQL Server cartridge: 
  2. Product documentation, including:

Installation instructions

For installation pre-requisites, permissions, information necessary to determine your environment’s hardware requirements, and for installation instructions, see the Foglight for Databases Deployment Guide.

Additional resources

Additional information is available from the following:


This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.

This release has the following known capabilities or limitations: The server will be enabled for Global Operation, but not localized to any particular locale.


About Us

We are more than just a name

We are on a quest to make your information technology work harder for you. That is why we build community-driven software solutions that help you spend less time on IT administration and more time on business innovation. We help you modernize your data center, get you to the cloud quicker and provide the expertise, security and accessibility you need to grow your data-driven business. Combined with Quest’s invitation to the global community to be a part of its innovation, and our firm commitment to ensuring customer satisfaction, we continue to deliver solutions that have a real impact on our customers today and leave a legacy we are proud of. We are challenging the status quo by transforming into a new software company. And as your partner, we work tirelessly to make sure your information technology is designed for you and by you. This is our mission, and we are in this together. Welcome to a new Quest. You are invited to Join the Innovation™.

Our brand, our vision. Together.

Our logo reflects our story: innovation, community and support. An important part of this story begins with the letter Q. It is a perfect circle, representing our commitment to technological precision and strength. The space in the Q itself symbolizes our need to add the missing piece — you — to the community, to the new Quest.

Contacting Quest

For sales or other inquiries, visit .

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:


Copyright© 2017 Quest Software Inc.

Quest, the Quest logo, Foglight, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. in the U.S.A. and other countries. For a complete list of Quest Software trademarks, please visit our website at Red Hat, JBoss, the JBoss logo, and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the U.S. and other countries. CentOS is a trademark of Red Hat, Inc. in the U.S. and other countries. Fedora and the Infinity design logo are trademarks of Red Hat, Inc. Microsoft, .NET, Active Directory, Internet Explorer, Hyper-V, Office 365, SharePoint, Silverlight,SQL Server, Visual Basic, Windows, Windows Vista and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. AIX, IBM, PowerPC, PowerVM, and WebSphere are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Java, Oracle, Oracle Solaris, PeopleSoft, Siebel, Sun, WebLogic, and ZFS are trademarks or registered trademarks of Oracle and/or its affiliates in the United States and other countries. SPARC is a registered trademark of SPARC International, Inc. in the United States and other countries. Products bearing the SPARC trademarks are based on an architecture developed by Oracle Corporation. OpenLDAP is a registered trademark of the OpenLDAP Foundation. HP is a registered trademark that belongs to HewlettPackard Development Company, L.P. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. Novell and eDirectory are registered trademarks of Novell, Inc., in the United States and other countries. VMware, ESX, ESXi, vSphere, vCenter, vMotion, and vCloud Director are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Sybase is a registered trademark of Sybase, Inc. The X Window System and UNIX are registered trademarks of The Open Group. Mozilla and Firefox are registered trademarks of the Mozilla Foundation. IOS is a registered trademark or trademark of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. Apple, iPad, iPhone, Mac OS, Safari, Swift, and Xcode are trademarks of Apple Inc., registered in the U.S. and other countries. Ubuntu is a registered trademark of Canonical Ltd. Symantec and Veritas are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. OpenSUSE, SUSE, and YAST are registered trademarks of SUSE LCC in the United States and other countries. Citrix, AppFlow, NetScaler, XenApp, and XenDesktop are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. PostgreSQL is a registered trademark of the PostgreSQL Global Development Group. MariaDB is a trademark or registered trademark of MariaDB Corporation Ab in the European Union and United States of America and/or other countries. Intel, Itanium, Pentium, and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries. Debian is a registered trademark of Software in the Public Interest, Inc. OpenStack is a trademark of the OpenStack Foundation. Amazon Web Services, the "Powered by Amazon Web Services" logo, and "Amazon RDS" are trademarks of, Inc. or its affiliates in the United States and/or other countries. Infobright, Infobright Community Edition and Infobright Enterprise Edition are trademarks of Infobright Inc. POLYCOM®, RealPresence® Collaboration Server, and RMX® are registered trademarks of Polycom, Inc. All other marks and names mentioned herein may be trademarks of their respective companies.