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.

SSDB-16092

When PI is enabled:

• Microsoft Visual C++ 2010 Redistributable Package or later needs to be installed on Foglight Management Server and Foglight Agent Manager.

• Mixed (Windows® and Linux®) environments are not supported.

n/a

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.

n/a

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

n/a

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

• Use WinRM which of course avoid the wmi issue

• Verify that enough permission are granted to WMI: https://support.quest.com/kb/90733

SSDB-15192

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

n/a

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

SSDB-14323

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

• Configuring the Command-Shell Connection Settings

• Configuring Windows Management Instrumentation

SSDB-13479

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

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

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.

SSDB-8388

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.

SSDB-7866

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

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.

SSDB-7090

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.

SSDB-7059

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

SSDB-3045

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

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

SSDB-5248

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

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.

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.

SSDB-10920

row_count metric is supported from SQL Server version 10.50.2500 and above

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.

SSDB-11283

Execution plan may not be resolved

SSDB-11657

Time range changes are not effecting the execution plan dashboard.

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.

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.