The following table shows the formulas for determining the memory size required for the execution of the optimizing information collection utility (pdgetcst).

Condition		Formula for determining memory size (KB)
HiRDB single server configuration		6,060 + 0.1 number of table storage RDAREAs + 0.07 number of index storage RDAREAs + 1.0 number of indexes + 0.04 number of tables in schema + 1.0 number of servers + 11 number of columns
HiRDB parallel server configuration	BES	1,813 + 0.06 number of table storage RDAREAs + 0.05 number of index storage RDAREAs + 0.03 number of indexes
	MGR	3,336 + 0.1 number of table storage RDAREAs + 0.07 number of index storage RDAREAs + 1.0 number of indexes + 0.04 number of tables in schema + 1.0 number of servers + 11 number of columns
	DS	16,402

Note

Other than these sizes, add the memory size used by the following SQL:

SELECT internal-information#, index-first-configuration-column-name FROM authorization-identifier, table-identifier ORDER BY primary-index-component-column-name WITHOUT LOCK NOWAIT;

SELECT FLOAT (COUNT(*)) FROM authorization-identifier.table-identifier WITHOUT LOCK NOWAIT;

SELECT FLOAT (COUNT(primary-index-component-column-name)) FROM authorization-identifier.table-identifier WITHOUT LOCK NOWAIT;

ALTER TABLE authorization-identifier.table-identifier CHANGE LOCK ROW;

#: The internal information is 12 bytes. Therefore, estimate as though an SQL statement were issued to retrieve a 12-byte character column (CHAR(12)), in addition to the index first configuration column name.

For details about the size of memory required by SQL, see the following sections:

• For a HiRDB single server configuration
  15.1.6 Formulas for size of memory required during SQL execution
  15.1.7 Formula for size of memory required during SQL preprocessing
  
• For a HiRDB parallel server configuration
  15.2.6 Formulas for size of memory required during SQL execution
  15.2.7 Formula for size of memory required during SQL preprocessing