Foglight for SQL Server (Cartridge) 7.3.0

サポートと今すぐチャット

Execution plan

Table 2. Execution plan related known issues
Issue 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 affecting 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.

Third party known issues

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

Table 3. Third-party known issues

Issue ID

Known issue

SSFOG-1716

No throughput data on dashboard for SSAS 2017 due to WMI class missing.

Workaround:

Download cumulative update package through https://support.microsoft.com/en-us/help/4056328/performance-counters-are-missing-after-the-installation-of-ssas-2017.

Install the package on the host where SSAS is installed.

Restart the host.

WCF-16277

Popup SQL Statement dialog cannot show all SQL text when accessing with Firefox browser using FMS version higher than 5.9.4.

FGL-20596

Cannot import license into installer with license file name XXX.lic.

Workaround:

When importing license into installer, change license file name to XXX.license.

Install xxx.lic after login FMS.

Change license file name to XXX.license and put it into license folder before FMS start up.

FOGDG-650

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.

FAM-7722

In FIPS-compliant mode, it is required to use at least 2048 RSA and DSA key size to do OS monitoring via SSH connection in DB cartridge.

When FglAM version is lower than 5.9.7.1, FglAM will not check RSA/DSA key size < 2048, and the connection is non-FIPS compliant.

Workaround: Upgrade the FglAM version to 5.9.7.1 or later.

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.

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® 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 or higher requires a workaround as follows:

Browse to https://support.quest.com/ and log in.

Perform solution https://support.quest.com/kb/SOL65870.

n/a

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, https://support.microsoft.com/kb/961435/en-us.

n/a

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

n/a

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"

n/a

The Foglight Time Bar Chart click event does not work with Chrome version 40.x.x.x and 39.x.x.x. Refer to https://code.google.com/p/chromium/issues/detail?id=428308 for more information.

n/a

The Windows System Center Endpoint Protection (SCEP) tool and Anti-Virus Protection tools installed on Windows® may negatively impact CPU and system performance of machines running Foglight, Foglight Agent Manager, and the SQL PI repository.

To reduce resource consumption it is highly recommended that you exclude the following directory from being scanned by the protection tools:

•

<installation directory>:\Quest\<FoglightAgentManager>

n/a

Anti-virus software may negatively impact the CPU and system performance of machines running Foglight. To reduce resource consumption, it is highly recommended to exclude the relevant directory, processes, and executables from being scanned by the anti-virus software. For detailed information, refer to the “Configuring anti-virus exclusion settings” in Installing Foglight on Windows with an Embedded PostgreSQL Database.

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