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 5.7.5.50 release of Foglight for SQL Server.
Review all sections before starting installation.

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

General Issues

Defect ID

Known Issue

SSFOG-775

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

SSFOG-739

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

SSFOG-736

DBSS_Error_Log_List collection may fail for SQL Server on Linux if SQL Server Agent is not running.

SSFOG-561

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.

SSFOG-558

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.

SSFOG-551

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.

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

SSFOG-442

Anti-Virus Protection tools may result in the failure
of setting up the installer agent, due to the occupied gar file. It is
highly recommended that you exclude
\deployed\downloaded from
directories being scanned by Anti-Virus Protection tools.

SSDB-16097

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
https://support.quest.com/kb/215054.

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.

SSDB-13199

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

SSDB-9277

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.

SSDB-9138

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’,1GO--To update the
currently configured value for advanced options.RECONFIGUREGO
—- To enable the feature.EXEC sp_configure ‘xp_cmdshell’, 1GO
—- To update the currently configured value for this feature.
RECONFIGUREGO

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.

SSDB-8949

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-5542

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.

SSDB-5248

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

SSDB-3061

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.

SSDB-3039

The DBSS- Deadlock Details alarm is disabled by
default.

SSDB-2455

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

SSDB-2379

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

SSDB-2060

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

Workaround: Implement trace flag -T1234

ODB-2984

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.

ODB-2829

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.

ODB-1606

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

n/a

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

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

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

n/a

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

n/a

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

Workaround:

For Windows® Vista® and Windows Server 2008:

According to http://support.microsoft.com/kb/929851, 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 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.

For Windows versions prior to Windows 2008/Vista:

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

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.

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

SSDB-11283

Execution plan may not be resolved

SSDB-11582

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.

SSDB-11657

Time range changes are not effecting the execution
plan dashboard.

n/a

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.

n/a

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.

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

Defect ID

Known Issue

n/a

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>

n/a

WMI-related issue

Problem: WMI
support is affected by the firewall

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

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

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.

According to Microsoft®
http://support.microsoft.com/kb/929851, 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.

n/a

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

n/a

Third Party Limitations

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

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.

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

c:\Infobright

c:\Quest\<FoglightAgentManager>

n/a

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

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
http://msdn.microsoft.com/en-us/library/aa394528%28VS.85%29.aspx

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:

If the agent is configured to use an IP address instead of the host name.

If the agent was not configured to monitor the operating system prior to the upgrade.

If the agent's host is currently monitored by the legacy OS cartridge (prior to version 5.6.4).

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

To upgrade Foglight for SQL Server:

Install version 5.7.5.50 of the cartridge as you would a new Foglight
for SQL Server cartridge. Do not delete the older version of the .car file.
Install version 5.7.5.50 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

Platform

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.

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

Foglight for SQL Server supports monitoring the following platforms:

Supported SQL Server versions:

SQL Server 2005 through 2016

Supported Operating Systems:

All Operating Systems supported by Microsoft®

Notes:

Foglight for SQL Server also supports the Express and
Developer editions of Microsoft® SQL Server.

Virtualization monitoring requires installing the VMware
tools service on the monitored VM.

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:

To verify TCP/IP connectivity for SQL statement collections, Management
Studio (SSMS) cannot be used as other protocols may be leveraged. Instead,
verify connectivity using a UDL as detailed here:
http://support.microsoft.com/kb/308075/

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.

Contents of the release package

Foglight for SQL Server User and Reference Guide (PDF and
online help)Note: This guide has not been updated
for this release. The previous version of this document is relevant for
the current release as well.

Foglight for Databases Deployment Guide (PDF)

Foglight for SQL Server Release Notes (this document)

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.

Globalization

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.

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

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
www.quest.com/legal. 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
Amazon.com, 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.