Physical memory (Agent for Microsoft SQL Server)
return to main contents page
return to "Application server" contents page
Note
The memory described here is the "virtual memory", which is the combination of the actual memory (the physical memory capacity that is actually required for each product) and the temporary area on the hard disk (the paging files 
or the swap files that are actually required for each product). If enough actual memory cannot be secured, the processing performance might be affected.
Table 1 Agent for Microsoft SQL Server memory requirements provides general estimates of the amount of memory required forAgent for Microsoft SQL Server. 
The term, initial conditions, refers to the condition of running one instance of Agent for Microsoft SQL Server.
Table 1 Agent for Microsoft SQL Server memory requirements
Status of Agent for�@Microsoft SQL Server Memory requirements (megabytes)
Windows Server
Operating under initial conditions 165 + J1 (see 1) + J2 (see 2)
Other than initial conditions (60 x I (see 8) + J1 (see1)) (see 6) + (105 x I (see8) + J2 (see 2)) (see 7)
Notes: 1. J = K1 +K2 +...+ KI (when operating under initial conditions, J = K1)
J is the total amount of memory required for each instance.
The value of K for each instance is calculated as follows:
- When collecting histories for PD_LD records (see 3)
K = (3 x a + 7 x b + 4 xc) / 1,024 (digits after the decimal point are rounded up)
- When not collecting histories for PD_LD records (and the conditions in 3 are not met)
K = (7 x b + 4 x c) / 1,024 (digits after the decimal point are rounded up)
Legend: a: Maximum number of lock requests processed on the monitoredMicrosoft SQL Server (see 9).
You can check the number of lock requests by using the following SQL statement from the user specified by the jpcinssetup command.
select count(*) from master..syslockinfo
b: Maximum number of processes running on the monitored Microsoft SQL Server. See 4 and 9.
You can check the number of processes by using the following SQL statement from the user specified by the jpcinssetup command.
select count(*) from master..sysprocesses
c: Maximum number of databases managed by the monitored Microsoft SQL Server instance. See 5 and 9.
You can check the number of databases by using the following SQL statement from the user specified by the jpcinssetup command.
select count(*) from master..sysdatabases
2. J2 = K1+ K2 +...KI (In case of operation in initial state, J2 = K1)
J2 is a sum of values of jpcagtq.exe for each instance.
The values of K of jpcagtq.exe for each instance are as follows:
When the historical information of PD_LD record is gathered:
K= (4 x a + 7 x b + 4 x c)/1024 (raise decimals to the next whole number)
When the historical information of PD_LD record is not gathered, and the condition described in Note 3 is not fulfilled:
K= (7 x b + 4 x c)/1024 (raise decimals to the next whole number)
For the value of a, b, and c, see Note 1
3. This formula is also applied when either of the following conditions is met:
- When displaying a real-time report whose data source is PD_LD records
- When Nuating an alarm whose data source is PD_LD records
4. If none of the following conditions are met, the value of b will be 0:
- When collecting histories for the records listed below
- When displaying a real-time report whose data source is the records listed below
- When Nuating alarms whose data source is the records listed below
PD_DD records
PD_LD records
PD_LOCK records
PD_PDET records
PD_RPDB records
PD_USER records
PD records
PI_DI records
PI_SI records
5. If none of the following conditions are met, the value of c will be 0:
- When collecting histories for the records listed below
- When displaying a real-time report whose data source is the records
listed below
- When Nuating an alarm whose data source is the records listed below
PD_DD records
PD_DS records
PD_LD records
PD_PDET records
PD_RD records
PD_RPDB records
PD_RS records
PD_SS records
PD records
PI_DI records
PI_SI records
6. Memory requirements for the jpcsto.exe process
7. Total memory requirements for the jpcagtq.exe process
8. Number of instances of Agent for Microsoft SQL Server
9. For details about the calculation of the instance number, see the following table:
Table_5_Methods_for_calculating_the_number_of_instances_for_records