지금 지원 담당자와 채팅
지원 담당자와 채팅

Foglight for Databases Shared 6.3.0 - Deployment Guide

SQL PI configured

SQL PI is available only for Oracle, SQL Server, SQL Server BI (Analysis services), and Azure SQL Database. These tables define the Hardware requirements for each server based on the number of monitoring agents

After locating your hardware requirements in each table, ensure that you complete the manual JVM Setting configuration as described in:

CPUs (2.4GHz)*

2 cores

4 cores

4 cores

4 cores

4 cores

6 cores

8 cores

RAM*

9GB

11GB

11GB

13GB

15GB

19GB

21GB

JVM Settings**

4096MB

4096MB

4096MB

6144MB

8192MB

10240MB

14336MB

Hard Drive Space

10GB

100GB

200GB

400GB

800GB

1200GB

1600GB

CPUs (2.4GHz)* — for a virtual machine the CPU reservation is highly recommended for better performance. The reservation is expressed in MHz.

RAM*- for a virtual machine the memory reservation is highly recommended for better performance.

 

CPUs (2.4GHz)*

1 core

4 cores

8 cores

8 cores

10 cores

12 cores

14 cores

RAM*

5GB

11GB

15GB

19GB

23GB

29GB

37GB

JVM Settings**

2048MB

7168MB

9216MB

13312MB

17408MB

23552MB

31744MB

Hard Drive Space

2GB

5GB

10GB

20GB

40GB

60GB

80GB

CPUs (2.4GHz)* - for a virtual machine the CPU reservation is highly recommended for better performance. The reservation is expressed in MHz.

RAM*- for a virtual machine the memory reservation is highly recommended for better performance.

Standard or Enterprise

Microsoft SQL Server 2016,2017,2019 and 2022

Supported on RDS and on Azure SQL Managed Instance*

Microsoft SQL Server 2016 for Windows* - Requires SP1 or SP2 for SQL Server 2016 Standard edition.

Amazon RDS for SQL Server 2016* - Requires SP1 or SP2 for SQL Server 2016 Standard edition.

Azure SQL Managed Instance*

Antivirus exclusions is required for the Microsoft SQL Server. For more information refer to the Microsoft’s official article How to choose antivirus software to run on computers that are running SQL Server.

CPUs (2.4GHz)*

4 cores

4 cores

6 cores

6 cores

8 cores

RAM*

20GB

32GB

42GB

60GB

64GB

Maximum SQL Server Memory

16384‬MB

26624MB

36864‬MB

55296MB

59392MB

Hard Drive Space*

Total 112GB

One disk

Total 224GB

Two disks

Total 383GB

Two disks

Total 547GB

Two disks

Total 1110GB

Two disks

RAM*- for a virtual machine the memory reservation is highly recommended for better performance.

Hard Drive Space* - the disk RPM is 15K. For 100 DB agents or above, RAID 5 disk (IOPS is above 1.2K) is required if the performance is downgraded. For 600 DB agents, 9K IOPS disk is required. For Azure SQL Managed instance 12500 IOPS per file and throughput 480MiB per file.

Raw Data* - raw performance data which is stored in 1-minute SQL PI tables.

Long-Term Data* - the low granularity data roll-up from raw data. Long-term (non 1-minute) data is stored in the primary filegroup in the SQL PI Repository. It is highly recommended to store database transaction log and temp database in a different disk with long-term data for better disk IO.

Transaction Log* - The frequency of the transaction log backup job is 2 hours.

All-in-One Installation

In the All-in-One installation, the Foglight Agent Manager is embedded. The Foglight Repository and SQL PI Repository are in the same SQL Server instance.

CPUs (2.4GHz)*

6 cores

RAM*

36GB

FMS JVM Settings

4096MB

FGLAM JVM Settings

6144MB

Maximum SQL Server Memory

20480MB

Hard Drive Space*

Total 160GB

Two disks

CPUs (2.4GHz)* - for a virtual machine the CPU reservation is highly recommended for better performance. The reservation is expressed in MHz.

RAM*- for a virtual machine the memory reservation is highly recommended for better performance.

Hard Drive Space* - the disk RPM is 15K. Extra hard drive space is needed for operating system storage.

 

SQL PI not configured

The table defines the Hardware requirements based on the number of monitoring agents.

After locating your hardware requirements in the tables, ensure that you complete the manual JVM Setting configuration as described in:

 

CPUs (2.4GHz)*

2 cores

4 cores

4 cores

4 cores

6 cores

8 cores

RAM*

6GB

8GB

10GB

12GB

16GB

18GB

JVM Settings**

4096MB

4096MB

6144MB

8192MB

10240MB

14336MB

Hard Drive Space

10GB

200GB

400GB

800GB

1200GB

1600GB

CPUs (2.4GHz)* - for a virtual machine the CPU reservation is highly recommended for better performance. The reservation is expressed in MHz.

RAM*- for a virtual machine the memory reservation is highly recommended for better performance.

 

CPUs (2.4GHz)*

1 core

2 cores

4 cores

4 cores

6 cores

8 cores

RAM*

1GB

4GB

6GB

10GB

14GB

18GB

JVM Settings**

256MB

2048MB

4096MB

8192MB

12288MB

16384MB

Hard Drive Space

2GB

5GB

10GB

20GB

30GB

40GB

CPUs (2.4GHz)* - for a virtual machine the CPU reservation is highly recommended for better performance. The reservation is expressed in MHz.

RAM*- for a virtual machine the memory reservation is highly recommended for better performance.

Manual configuration requirement for SQL PI Repository

 

Log in to the SQL Server through SSMS client. Edit the Maximum server memory in Server Properties dialog. For SQL PI Agents number less than 50, set the Maximum SQL Server Memory to 16384 MB. For All-in-One installation, refer to Table 4 row Maximum SQL Server Memory. For others, refer to Table 3 row Maximum SQL Server Memory.

Edit the server.config file located under the <Foglight installation directory>\config directory.

For 4096MB, add the following lines:

server.vm.option0 = "-Xms4096m";

server.vm.option1 = "-Xmx4096m";

Edit the baseline.jvmargs.config file located under the <Agent Manager installation directory>\state\default\config\ directory

For 2048MB, add the following lines:

vmparameter.0 = "-Xms2048m";

vmparameter.1 = "-Xmx2048m";

For number of agents > 50, edit these settings:

Data submission channel — edit the fglam.config.xml file located under the <Agent Manager installation directory>\state\default\config\ directory
Number of OS connections — edit the baseline.jvmargs.config file located under the <Agent Manager installation directory>\state\default\config\ directory
NOTE: In the example above, “1024” is a placeholder. The suggested value of maxActiveConnectionsCap is the number of database agents multiplied by 3.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택