Appendix D.2 Data manipulation SQLs
- Organization of this subsection
- (1) SELECT (non-temporary table with LOCK TABLE not specified, WITHOUT LOCK not specified)
- (2) SELECT (non-temporary table with LOCK TABLE not specified, WITHOUT LOCK WAIT specified)
- (3) SELECT (non-temporary table with LOCK TABLE not specified, WITHOUT LOCK NOWAIT specified)
- (4) SELECT (temporary table, or non-temporary table with LOCK TABLE specified#1)
- (5) INSERT (non-temporary table with INSERT to VALUES clauses specified, and LOCK TABLE not specified)
- (6) INSERT (non-temporary table with INSERT to VALUES clauses specified, and LOCK TABLE specified#1)
- (7) INSERT (INSERT to SELECT clauses specified)
- (8) INSERT (non-temporary table with INSERT to VALUES clauses specified, LOCK TABLE not specified, and index key value no locking used)
- (9) INSERT (temporary table, or INSERT to VALUES clauses specified, LOCK TABLE specified#4, and index key value no locking used)
- (10) INSERT (INSERT to SELECT clauses specified, index key value no locking used).
- (11) UPDATE (non-temporary table with LOCK TABLE not specified)
- (12) UPDATE (temporary table or LOCK TABLE is specified#1)
- (13) UPDATE (non-temporary table with LOCK TABLE not specified and index key value no locking used)
- (14) UPDATE (temporary table, or LOCK TABLE specified#5 and index key value no locking used)
- (15) DELETE (non-temporary table with LOCK TABLE not specified)
- (16) DELETE (temporary table, or LOCK TABLE specified and index key value no locking used#1)
- (17) DELETE (non-temporary table with LOCK TABLE not specified and index key value no locking used)
- (18) DELETE (temporary table, or LOCK TABLE specified#6 and index key value no locking used)
- (19) PURGE TABLE
- (20) ASSIGN LIST statement (list creation from a base table)
- (21) ASSIGN LIST statement (list creation from a list)
- (22) ASSIGN LIST statement (list name change)
- (23) DROP LIST statement (deletion with list name specification: DROP LIST ~)
- (24) DROP LIST statement (deletion of all lists locally owned: DROP ALL LIST ~)
- (25) Number of lock requests in preprocessing
(1) SELECT (non-temporary table with LOCK TABLE not specified, WITHOUT LOCK not specified)
(a) For a HiRDB single server configuration
[preprocessing]#1 + number of RDAREAs storing tables to be retrieved + number of tables + number of hit retrieval rows#3 + number of RDAREAs storing the indexes used#2 + number of index keys used in retrieval#5
- Add the following if an index-type plug-in is used for retrieval or if a data-type plug-in is defined in the columns to be referenced:
- + number of logical files used by the plug-in#4
- Note the following if table data is retrieved via a list:
- Determine the number of lock requests that occur in the preprocessing part of the formula by applying the preprocessing formula to the list's base tables.
- Determine the number of RDAREAs storing tables to be retrieved and the number of tables in the formula for the list's base tables.
- The following value must be added:
+ 1
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs storing tables to be retrieved + number of RDAREAs storing the indexes used
- Add the following if routines are used for retrieval:
- + number of routines used + 1
(b) For a HiRDB parallel server configuration (front-end and dictionary servers)
[preprocessing]#1
If table data is retrieved via a list, determine the number of lock requests that occur in the preprocessing part of the formula by applying the preprocessing formula to the list's base tables.
- Add the following if routines are used for retrieval:
- + number of routines used + 1
(c) For a HiRDB parallel server configuration (back-end server)
number of RDAREAs storing tables to be retrieved + number of tables + number of hit retrieval rows#3 + number of RDAREAs storing the indexes used#2 + number of index keys used in retrieval#5
- Add the following if an index-type plug-in is used for retrieval or if a data-type plug-in is defined in the columns to be referenced:
- + number of logical files used by the plug-in#4
- Note the following if table data is retrieved via a list:
- Determine the number of RDAREAs storing the tables to be retrieved and the number of tables in the formula for the list's base tables.
- The following value must be added:
+ 1
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs storing tables to be retrieved + number of RDAREAs storing the indexes used
- Add the following if routines are used for retrieval:
- + number of routines used + 1
- #1: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
- #2: If indexes are defined for columns specified with AND or OR in a retrieval condition expression, those indexes will be used as a rule.
- #3:
- If data is to be retrieved from multiple tables, determine the number of hit retrieval rows in individual tables and add that number.
- If two or more conditions are specified for index definition columns (one or more if FOR UPDATE is specified), determine the combined total of the rows that are retrieved based only on the conditions for each index.
- Determine the number of hit retrieval rows after excluding conditions that use the columns of multiple tables and conditions that use functions.
- Use the number of hit retrieval pages if a lock is specified for each page.
- #4: For the number of logical files used by plug-ins, see the manuals included with the plug-ins.
- #5: The value is 1 if index key value lock is specified, and 0 if index key value lock is not specified.
(2) SELECT (non-temporary table with LOCK TABLE not specified, WITHOUT LOCK WAIT specified)
(a) For a HiRDB single server configuration
[preprocessing]#1 + number of RDAREAs to be retrieved + number of tables + 1 + number of RDAREAs storing the indexes used#2 + number of index keys used in retrieval#4
- Add the following if an index-type plug-in is used for retrieval or if a data-type plug-in is defined in the columns to be referenced:
- + number of logical files used by the plug-in#3
- Note the following if table data is retrieved via a list:
- Determine the number of lock requests that occur in the preprocessing part of the formula by applying the preprocessing formula to the list's base tables.
- Determine the number of RDAREAs storing the tables to be retrieved and the number of tables in the formula for the list's base tables.
- The following value must be added:
+ 1
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be retrieved + number of RDAREAs storing the indexes used
- Add the following if routines are used for retrieval:
- + number of routines used + 1
(b) For a HiRDB parallel server configuration (front-end and dictionary servers)
[preprocessing]#1
If table data is retrieved via a list, determine the number of lock requests that occur in the preprocessing part of the formula by applying the preprocessing formula to the list's base tables.
- Add the following if routines are used for retrieval:
- + number of routines used + 1
(c) For a HiRDB parallel server configuration (back-end server)
number of RDAREAs to be retrieved + number of tables + 2 + number of RDAREAs storing the indexes used#2 + number of index keys used in retrieval#4
- Add the following if an index-type plug-in is used for retrieval or if a data-type plug-in is defined in the columns to be referenced:
- + number of logical files used by the plug-in#3
- Note the following if table data is retrieved via a list:
- Determine the number of RDAREAs storing tables to be retrieved and the number of tables in the formula for the list's base tables.
- The following value must be added:
+ 1
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be retrieved + number of RDAREAs storing the indexes used
- Add the following if routines are used for retrieval:
- + number of routines used + 1
#1: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
#2: If indexes are defined for columns specified with AND or OR in a retrieval condition expression, those indexes will be used as a rule.
#3: For the number of logical files used by plug-ins, refer to the manuals included with the plug-ins.
- #4: The value is 1 if index key value lock is specified, and 0 if index key value lock is not specified.
(3) SELECT (non-temporary table with LOCK TABLE not specified, WITHOUT LOCK NOWAIT specified)
(a) For a HiRDB single server configuration
[preprocessing]#1 + number of RDAREAs to be retrieved + number of tables + number of RDAREAs storing the indexes used#2
- Add the following if an index-type plug-in is used for retrieval or if a data-type plug-in is defined in the columns to be referenced:
- + number of logical files used by the plug-in#3
- Note the following if table data is retrieved via a list:
- Determine the number of lock requests that occur in the preprocessing part of the formula by applying the preprocessing formula to the list's base tables.
- Determine the number of RDAREAs storing tables to be retrieved and the number of tables in the formula for the list's base tables.
- The following value must be added:
+ 1
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be retrieved + number of RDAREAs storing the indexes used
- Add the following if LOCK is specified for the pd_nowait_scan_option operand (add only for non-FIX tables):
- + 1
- Add the following if routines are used for retrieval:
- + number of routines used + 1
(b) For a HiRDB parallel server configuration (front-end and dictionary servers)
[preprocessing]#1
If table data is retrieved via a list, determine the number of lock requests that occur in the preprocessing part of the formula by applying the preprocessing formula to the list's base tables.
- Add the following if routines are used for retrieval:
- + number of routines used + 1
(c) For a HiRDB parallel server configuration (back-end server)
number of RDAREAs to be retrieved + number of tables + number of RDAREAs storing the indexes used#2
- Add the following if an index-type plug-in is used for retrieval or if a data-type plug-in is defined in the columns to be referenced:
- + number of logical files used by the plug-in#3
- Note the following if table data is retrieved via a list:
- Determine the number of RDAREAs storing tables to be retrieved and the number of tables in the formula for the list's base tables.
- The following value must be added:
+ 1
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be retrieved + number of RDAREAs storing the indexes used
- Add the following if LOCK is specified for the pd_nowait_scan_option operand (add only for non-FIX tables):
- + 1
- Add the following if routines are used for retrieval:
- + number of routines used + 1
#1: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
#2: If indexes are defined for columns specified with AND or OR in a retrieval condition expression, those indexes will be used as a rule.
#3: For the number of logical files used by plug-ins, refer to the manuals included with the plug-ins.
(4) SELECT (temporary table, or non-temporary table with LOCK TABLE specified#1)
(a) For a HiRDB single server configuration
[preprocessing]#2 + number of RDAREAs to be retrieved + number of RDAREAs storing the indexes used
- Add the following if an index-type plug-in is used for retrieval or if a data-type plug-in is defined in the columns to be referenced:
- + number of logical files used by the plug-in#3
- Note the following if table data is retrieved via a list:
- Determine the number of lock requests that occur in the preprocessing part of the formula by applying the preprocessing formula to the list's base tables.
- Determine the number of RDAREAs storing tables to be retrieved and the number of tables in the formula for the list's base tables.
- The following value must be added:
+ 1
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be retrieved + number of RDAREAs storing the indexes used
- Add the following if routines are used for retrieval:
- + number of routines used + 1
(b) For a HiRDB parallel server configuration (front-end and dictionary servers)
[preprocessing]#2
If table data is retrieved via a list, determine the number of lock requests that occur in the preprocessing part of the formula by applying the preprocessing formula to the list's base tables.
- Add the following if routines are used for retrieval:
- + number of routines used + 1
(c) For a HiRDB parallel server configuration (back-end server)
number of RDAREAs to be retrieved + number of RDAREAs storing the indexes used
- Add the following if an index-type plug-in is used for retrieval or if a data-type plug-in is defined in the columns to be referenced:
- + number of logical files used by the plug-in#3
- Note the following if table data is retrieved via a list:
- Determine the number of RDAREAs storing tables to be retrieved and the number of tables in the formula for the list's base tables.
- The following value must be added:
+ 1
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be retrieved + number of RDAREAs storing the indexes used
- Add the following if routines are used for retrieval:
- + number of routines used + 1
#1: If LOCK TABLE IN SHARE MODE is specified for SELECT with FOR UPDATE specified, the formula is the same as when LOCK TABLE in not specified.
#2: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
#3: For the number of logical files used by plug-ins, refer to the manuals included with the plug-ins.
(5) INSERT (non-temporary table with INSERT to VALUES clauses specified, and LOCK TABLE not specified)
(a) For a HiRDB single server configuration
[preprocessing]#1 + 5 + number of RDAREAs to be inserted#3 + number of inserted VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger
number of branched rows + number of inserted BINARY-type columns that cannot be stored in one page
number of branched rows + number of indexes
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#2
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be inserted
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for insertion:
- + number of sequence generators used
2
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#1
- Add the following if routines are used for insertion:
- + number of routines used + 1
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]#1
(d) For a HiRDB parallel server configuration (back-end server)
5 + number of RDAREAs to be inserted#3 + number of inserted VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger
number of branched rows + number of inserted BINARY-type columns that cannot be stored in one page
number of branched rows + number of indexes
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#2
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be inserted
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for insertion:
- + number of sequence generators used
2
#1: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
#2: For the number of logical files used by plug-ins, refer to the manuals included with the plug-ins.
#3: Total number of RDAREAs for the target tables, indexes, LOB columns, and LOB attributes.
(6) INSERT (non-temporary table with INSERT to VALUES clauses specified, and LOCK TABLE specified#1)
(a) For a HiRDB single server configuration
[preprocessing]#2 + 1 + number of RDAREAs to be inserted#4
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#3
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be inserted
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if inserting to an SQL session-specific temporary table:
- + number of SQL session-specific temporary tables that are used
- Add the following if inserting to a temporary table:
- + 2
- Add the following if sequence generators (NEXT VALUE expressions) are used for insertion:
- + number of sequence generators used
2
- Add the following if inserting to a temporary table:
- + 5
- + 2
number of temporary table indexes - + 3
number of temporary table RDAREAs within the single server - + total number of segments used by temporary tables and temporary table indexes
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#2
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if inserting to an SQL session-specific temporary table:
- + number of SQL session-specific temporary tables that are used
- Add the following if inserting to a temporary table:
- + 2
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]#2
(d) For a HiRDB parallel server configuration (back-end server)
1 + number of RDAREAs to be inserted#4
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#3
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be inserted
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for insertion:
- + number of sequence generators used
2
- Add the following if inserting to a temporary table:
- + 5
- + 2
number of temporary table indexes - + 3
number of temporary table RDAREAs within the back-end server - + total number of segments used by temporary tables and temporary table indexes
#1: If LOCK TABLE IN SHARE MODE is specified for a non-temporary table, the formula is the same as when LOCK TABLE is not specified.
#2: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
#3: For the number of logical files used by plug-ins, refer to the manuals included with the plug-ins.
#4: Total number of RDAREAs for the target indexes, LOB columns, and LOB attributes.
(7) INSERT (INSERT to SELECT clauses specified)
(a) For a HiRDB single server configuration
[preprocessing]#1 + number of RDAREAs to be inserted#5 + 4 + number of inserted rows#2, #6 + number of columns of inserted rows of VARCHAR, NVARCHAR, or MVARCHAR that are 256 bytes or larger
number of inserted rows#2, #6
number of branched rows + number of inserted BINARY-type columns that cannot be stored in one page
number of inserted rows#2, #6
number of branched rows + number of inserted rows#6
number of indexes + 1 + number of RDAREAs to be retrieved#5 + number of tables to be retrieved + number of hit retrieval rows#3, #6
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-ins to be inserted#4 + number of logical files used by the plug-ins used for retrieval#4
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be inserted + number of RDAREAs to be retrieved
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if inserting to an SQL session-specific temporary table:
- + number of SQL session-specific temporary tables that are used
- Add the following if inserting to a temporary table:
- + 2
- Add the following if sequence generators (NEXT VALUE expressions) are used for insertion:
- + number of sequence generators used
2
- Add the following if inserting to a temporary table:
- + 2 + 2
number of temporary table indexes - + number of temporary table RDAREAs within the single server
3 - + total number of segments used by temporary tables and temporary table indexes
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#1
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if inserting to an SQL session-specific temporary table:
- + number of SQL session-specific temporary tables that are used
- Add the following if inserting to a temporary table:
- + 2
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]#1
- Add the following if routines are used for insertion:
- + number of routines used + 1
(d) For a HiRDB parallel server configuration (back-end server)
4 + number of RDAREAs to be inserted#5 + number of inserted rows#2, #6 + number of columns of inserted rows of VARCHAR, NVARCHAR, or MVARCHAR that are 256 bytes or larger
number of inserted rows#6
number of branched rows + number of inserted BINARY-type columns that cannot be stored in one page
number of inserted rows#6
number of branched rows + number of inserted rows#6
number of indexes + 1 + number of RDAREAs to be retrieved#5 + number of tables to be retrieved + number of hit retrieval rows#3, #6
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-ins to be inserted#4 + number of logical files used by the plug-ins used for retrieval#4
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be inserted + number of RDAREAs to be retrieved
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for insertion:
- + number of sequence generators used
2
- Add the following if inserting to a temporary table:
- + 2 + 2
number of temporary table indexes - + number of temporary table RDAREAs within the back-end server
3 - + total number of segments used by temporary tables and temporary table indexes
- #1: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
- #2: Use the number of pages inserted if locking by page is specified.
- #3:
- If data is to be retrieved from multiple tables, determine the number of hit retrieval rows in individual tables and add that number.
- If two or more conditions are specified for index definition columns, determine the combined total of the rows that are retrieved based only on the conditions for each index.
- Determine the number of hit retrieval rows after excluding conditions that use the columns of multiple tables and conditions that use functions.
- Use the number of hit retrieval pages if a lock is specified for each page.
- #4: For the number of logical files used by plug-ins, refer to the manuals included with the plug-ins.
- #5: Total number of RDAREAs for the target tables, indexes, LOB columns, and LOB attributes.
- #6: For a temporary table, the value is 0.
(8) INSERT (non-temporary table with INSERT to VALUES clauses specified, LOCK TABLE not specified, and index key value no locking used)
(a) For a HiRDB single server configuration
[preprocessing]#1 + 5 + number of RDAREAs to be inserted#2 + number of inserted VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger
number of branched rows + number of inserted BINARY-type columns that cannot be stored in one page
number of branched rows + 1
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#3
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be inserted
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for insertion:
- + number of sequence generators used
2
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#1
- Add the following if routines are used for insertion:
- + number of routines used + 1
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]#1
(d) For a HiRDB parallel server configuration (back-end server)
5 + number of RDAREAs to be inserted#2 + number of inserted VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger
number of branched rows + number of inserted BINARY-type columns that cannot be stored in one page
number of branched rows + 1
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#3
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be inserted
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for insertion:
- + number of sequence generators used
2
#1: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
#2: Total number of RDAREAs for the target tables, indexes, LOB columns, and LOB attributes.
#3: For the number of logical files used by each plug-in, refer to the manual provided with the plug-in.
(9) INSERT (temporary table, or INSERT to VALUES clauses specified, LOCK TABLE specified#4, and index key value no locking used)
(a) For a HiRDB single server configuration
[preprocessing]#1 + 1 + number of RDAREAs to be inserted#2
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#3
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be inserted
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if inserting to an SQL session-specific temporary table:
- + number of SQL session-specific temporary tables that are used
- Add the following if inserting to a temporary table:
- + 2
- Add the following if sequence generators (NEXT VALUE expressions) are used for insertion:
- + number of sequence generators used
2
- Add the following if inserting to a temporary table:
- + 5
- + 2
number of temporary table indexes - + 3
number of temporary table RDAREAs within the single server - + total number of segments used by temporary tables and temporary table indexes
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#1
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if inserting to an SQL session-specific temporary table:
- + number of SQL session-specific temporary tables that are used
- Add the following if inserting to a temporary table:
- + 2
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]#1
(d) For a HiRDB parallel server configuration (back-end server)
- 1 + number of RDAREAs to be inserted#2
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#3
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be inserted
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for insertion:
- + number of sequence generators used
2
- Add the following if inserting to a temporary table:
- + 5
- + 2
number of temporary table indexes - + 3
number of temporary table RDAREAs within the back-end server - + total number of segments used by temporary tables and temporary table indexes
#1: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
#2: Total number of RDAREAs for the target indexes, LOB columns, and LOB attributes.
#3: For the number of logical files used by each plug-in, refer to the manual provided with the plug-in.
#4: If LOCK TABLE IN SHARE MODE is specified for a non-temporary table, the formula is the same as when LOCK TABLE is not specified.
(10) INSERT (INSERT to SELECT clauses specified, index key value no locking used).
(a) For a HiRDB single server configuration
[preprocessing]#1 + number of RDAREAs to be inserted#2 + 4 + number of inserted rows#3, #6 + number of inserted VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger
number of inserted rows#6
number of branched rows + number of inserted BINARY-type columns that cannot be stored in one page
number of inserted rows#6
number of branched rows + number of indexes + 1 + number of RDAREAs to be retrieved#2 + number of tables to be retrieved + number of hit retrieval rows#4, #6
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-ins to be inserted#5 + number of logical files used by the plug-ins used for retrieval#5
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be inserted + number of RDAREAs to be retrieved
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if inserting to an SQL session-specific temporary table:
- + number of SQL session-specific temporary tables that are used
- Add the following if inserting to a temporary table:
- + 2
- Add the following if sequence generators (NEXT VALUE expressions) are used for insertion:
- + number of sequence generators used
2
- Add the following if inserting to a temporary table:
- + 2
- + 2
number of temporary table indexes - + 3
number of temporary table RDAREAs within the server - + total number of segments used by temporary tables and temporary table indexes
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#1
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if inserting to an SQL session-specific temporary table:
- + number of SQL session-specific temporary tables that are used
- Add the following if inserting to a temporary table:
- + 2
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]#1
- Add the following if routines are used for insertion:
- + number of routines used + 1
(d) For a HiRDB parallel server configuration (back-end server)
number of RDAREAs to be inserted#2 + 4 + number of inserted rows#3, #6 + number of inserted VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger
number of inserted rows#6
number of branched rows + number of inserted BINARY-type columns that cannot be stored in one page
number of inserted rows#6
number of branched rows + number of indexes + 1 + number of RDAREAs to be retrieved#2 + number of tables to be retrieved + number of hit retrieval rows#4, #6
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-ins to be inserted#5 + number of logical files used by the plug-ins used for retrieval#5
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be inserted + number of RDAREAs to be retrieved
- Add the following if routines are used for insertion:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for insertion:
- + number of sequence generators used
2
- Add the following if inserting to a temporary table:
- + 2
- + 2
number of temporary table indexes - + 3
number of temporary table RDAREAs within the back-end server - + total number of segments used by temporary tables and temporary table indexes
- #1: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
- #2: Total number of RDAREAs for the target tables, indexes, LOB columns, and LOB attributes.
- #3: Use the number of inserted pages if a lock is specified for each page.
- #4:
- If data is to be retrieved from multiple tables, determine the number of hit retrieval rows in individual tables and add that number.
- If two or more conditions are specified for index definition columns, determine the combined total of the rows that are retrieved based only on the conditions for each index.
- Determine the number of hit retrieval rows after excluding conditions that use the columns of multiple tables and conditions that use functions.
- Use the number of hit retrieval pages if a lock is specified for each page.
#5: For the number of logical files used by each plug-in, refer to the manual provided with the plug-in.
- #6: For a temporary table, the value is 0.
(11) UPDATE (non-temporary table with LOCK TABLE not specified)
(a) For a HiRDB single server configuration
[preprocessing]#1 + number of RDAREAs to be updated#5 + 4 + number of updated rows#2 + number of pre-update VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger
number of pre-update rows
number of branched rows before update + number of post-update VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger
number of post-update rows
number of branched rows after update + number of pre-update BINARY-type columns that cannot be stored in one page
number of pre-update rows
number of branched rows before update + number of post-update BINARY-type columns that cannot be stored in one page
number of post-update rows
number of branched rows after update + number of indexes to be updated
2
number of updated rows +
(number of segments storing pre-update LOB data)#4
- Add the following if a data-type plug-in or index-type plug-in is defined for the columns to be updated:
- + number of logical files used by the plug-in#3
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be updated
- Add the following if LOCK is specified for the pd_nowait_scan_option operand (add only for a non-FIX table):
- + 1
- Add the following if routines are used for updating:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for updating:
- + number of sequence generators used
2
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#1
- Add the following if routines are used for updating:
- + number of routines used + 1
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]#1
(d) For a HiRDB parallel server configuration (back-end server)
number of RDAREAs to be updated#5 + 4 + number of updated rows#2 + number of pre-update VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger
number of pre-update rows
number of branched rows before update + number of post-update VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger
number of post-update rows
number of branched rows after update + number of pre-update BINARY-type columns that cannot be stored in one page
number of pre-update rows
number of branched rows before update + number of post-update BINARY-type columns that cannot be stored in one page
number of post-update rows
number of branched rows after update + number of indexes to be updated
2
number of updated rows +
(number of segments storing pre-update LOB data)#4
- Add the following if a data-type plug-in or index-type plug-in is defined for the columns to be updated:
- + number of logical files used by the plug-in#3
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be updated
- Add the following if LOCK is specified for the pd_nowait_scan_option operand (add only for a non-FIX table):
- + 1
- Add the following if routines are used for updating:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for updating:
- + number of sequence generators used
2
- #1: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
- #2
- If there is a conditional expression that needs to retrieve data from another table, determine the number of hit retrieval rows for that table and add it to the number of updated rows.
- If conditions are specified for an index definition column, determine the combined total of the rows that are retrieved based only on the conditions for each index. Then, use the number of hit retrieval rows as the number of updated rows.
- Determine the number of hit retrieval rows after excluding conditions that use the columns of multiple tables and conditions that use functions. Then, use the number of hit retrieval rows as the number of updated rows.
- Use the number of updated pages if a lock is specified for each page.
- #3: For the number of logical files used by plug-ins, refer to the manuals included with the plug-ins.
- #4: Repeat and add this for the number of LOB columns and LOB attributes.
- #5: Total number of RDAREAs for the target tables, indexes, LOB columns, and LOB attributes.
(12) UPDATE (temporary table or LOCK TABLE is specified#1)
(a) For a HiRDB single server configuration
[preprocessing]#2 + number of RDAREAs to be updated#5 + 1 +
(number of segments storing pre-update LOB data)#4
- Add the following if a data-type plug-in or index-type plug-in is defined for the columns to be updated:
- + number of logical files used by the plug-in#3
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be updated
- Add the following if LOCK is specified for the pd_nowait_scan_option operand (add only for a non-FIX table):
- + 1
- Add the following if routines are used for updating:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for updating:
- + number of sequence generators used
2
- Add the following if temporary tables are used for updating:
- + total number of segments used by temporary tables and temporary table indexes
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#2
- Add the following if routines are used for updating:
- + number of routines used + 1
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]#2
(d) For a HiRDB parallel server configuration (back-end server)
number of RDAREAs to be updated#5 + 1 +
(number of segments storing pre-update LOB data)#4
- Add the following if a data-type plug-in or index-type plug-in is defined for the columns to be updated:
- + number of logical files used by the plug-in#3
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be updated
- Add the following if LOCK is specified for the pd_nowait_scan_option operand (add only for a non-FIX table):
- + 1
- Add the following if routines are used for updating:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for updating:
- + number of sequence generators used
2
- Add the following if temporary tables are used for updating:
- + total number of segments used by temporary tables and temporary table indexes
#1: If LOCK TABLE IN SHARE MODE is specified for a non-temporary table, the formula is the same as when LOCK TABLE is not specified.
#2: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
#3: For the number of logical files used by plug-ins, refer to the manuals included with the plug-ins.
#4: Repeat and add this for the number of LOB columns and LOB attributes.
#5: Total number of RDAREAs for the target indexes, LOB columns, and LOB attributes.
(13) UPDATE (non-temporary table with LOCK TABLE not specified and index key value no locking used)
(a) For a HiRDB single server configuration
[preprocessing]#1 + number of RDAREAs to be updated#2 + 4 + number of updated rows#3 + number of pre-update VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger
number of pre-update rows
number of branched rows before update + number of post-update VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger
number of post-update rows
number of branched rows after update + number of pre-update BINARY-type columns that cannot be stored in one page
number of pre-update rows
number of branched rows before update + number of post-update BINARY-type columns that cannot be stored in one page
number of post-update rows
number of branched rows after update +
(number of segments storing pre-update LOB data)#4
- Add the following if a data-type plug-in or index-type plug-in is defined for the columns to be updated:
- + number of logical files used by the plug-in#5
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be updated
- Add the following if LOCK is specified for the pd_nowait_scan_option operand (add only for a non-FIX table):
- + 1
- Add the following if routines are used for updating:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for updating:
- + number of sequence generators used
2
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#1
- Add the following if routines are used for updating:
- + number of routines used + 1
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]#1
(d) For a HiRDB parallel server configuration (back-end server)
number of RDAREAs to be updated#2 + 4 + number of updated rows#3 + number of pre-update VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger
number of pre-update rows
number of branched rows before update + number of post-update VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger
number of post-update rows
number of branched rows after update + number of pre-update BINARY-type columns that cannot be stored in one page
number of pre-update rows
number of branched rows before update + number of post-update BINARY-type columns that cannot be stored in one page
number of post-update rows
number of branched rows after update +
(number of segments storing pre-update LOB data)#4
- Add the following if a data-type plug-in or index-type plug-in is defined for the columns to be updated:
- + number of logical files used by the plug-in#5
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be updated
- Add the following if LOCK is specified for the pd_nowait_scan_option operand (add only for a non-FIX table):
- + 1
- Add the following if routines are used for updating:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for updating:
- + number of sequence generators used
2
- #1: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
- #2: Total number of RDAREAs for the target tables, indexes, LOB columns, and LOB attributes.
- #3
- If there is a conditional expression that needs to retrieve data from another table, determine the number of hit retrieval rows for that table and add it to the number of updated rows.
- If conditions are specified for an index definition column, determine the combined total of the rows that are retrieved based only on the conditions for each index. Then, use the number of hit retrieval rows as the number of updated rows.
- Determine the number of hit retrieval rows after excluding conditions that use the columns of multiple tables and conditions that use functions. Then, use the number of hit retrieval rows as the number of updated rows.
- Use the number of updated pages if a lock is specified for each page. If a unique index is defined for the table, also add the value for the rows to be updated.
- #4: Repeat and add this for the number of LOB columns and LOB attributes.
#5: For the number of logical files used by each plug-in, refer to the manual provided with the plug-in.
(14) UPDATE (temporary table, or LOCK TABLE specified#5 and index key value no locking used)
(a) For a HiRDB single server configuration
[preprocessing]#1 + number of RDAREAs to be updated#2 + 1 +
(number of segments storing pre-update LOB data)#3
- Add the following if a data-type plug-in or index-type plug-in is defined for the columns to be updated:
- + number of logical files used by the plug-in#4
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be updated
- Add the following if LOCK is specified for the pd_nowait_scan_option operand (add only for a non-FIX table):
- + 1
- Add the following if routines are used for updating:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for updating:
- + number of sequence generators used
2
- Add the following if temporary tables are used for updating:
- + total number of segments used by temporary tables and temporary table indexes
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#1
- Add the following if routines are used for updating:
- + number of routines used + 1
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]#1
(d) For a HiRDB parallel server configuration (back-end server)
number of RDAREAs to be updated#2 + 1 +
(number of segments storing pre-update LOB data)#3
- Add the following if a data-type plug-in or index-type plug-in is defined for the columns to be updated:
- + number of logical files used by the plug-in#4
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be updated
- Add the following if LOCK is specified for the pd_nowait_scan_option operand (add only for a non-FIX table):
- + 1
- Add the following if routines are used for updating:
- + number of routines used + 1
- Add the following if sequence generators (NEXT VALUE expressions) are used for updating:
- + number of sequence generators used
2
- Add the following if temporary tables are used for updating:
- + total number of segments used by temporary tables and temporary table indexes
#1: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
#2: Total number of RDAREAs for the indexes, LOB columns, and LOB attributes.
#3: Repeat and add this for the number of LOB columns and LOB attributes.
#4: For the number of logical files used by each plug-in, refer to the manual provided with the plug-in.
#5: If LOCK TABLE IN SHARE MODE is specified for a non-temporary table, the formula is the same as when LOCK TABLE is not specified.
(15) DELETE (non-temporary table with LOCK TABLE not specified)
(a) For a HiRDB single server configuration
[preprocessing]#1 + number of RDAREAs to be deleted#5 + 1 + number of deleted rows#2 + number of VARCHAR, NVARCHAR, or MVARCHAR columns deleted that are 256 bytes or larger
number of branched rows
number of deleted rows + number of BINARY-type columns to be deleted that cannot be stored in one page
number of branched rows
number of deleted rows + number of indexes
number of deleted rows +
(number of deleted LOB data segments + number of segments storing the deleted LOB data)#4
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#3
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be deleted
- Add the following if routines are used for deletion:
- + number of routines used + 1
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#1
- Add the following if routines are used for deletion:
- + number of routines used + 1
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]#1
(d) For a HiRDB parallel server configuration (back-end server)
number of RDAREAs to be deleted#5 + 1 + number of deleted rows#2 + number of VARCHAR, NVARCHAR, or MVARCHAR columns deleted that are 256 bytes or larger
number of branched rows
number of deleted rows + number of BINARY-type columns to be deleted that cannot be stored in one page
number of branched rows
number of deleted rows + number of indexes
number of deleted rows +
(number of deleted LOB data segments + number of segments storing the deleted LOB data)#4
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#3
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be deleted
- Add the following if routines are used for deletion:
- + number of routines used + 1
- #1: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
- #2
- If there is a conditional expression that needs to retrieve data from another table, determine the number of hit retrieval rows for that table and add that value to the number of deleted rows.
- If conditions are specified for index definition columns, determine the combined total of the rows that are retrieved based only on the conditions for each index. Then, use the number of hit retrieval rows as the number of deleted rows.
- Determine the number of hit retrieval rows after excluding conditions that use the columns of multiple tables and conditions that use functions. Then, use the number of hit retrieval rows as the number of deleted rows.
- Use the number of deleted pages if a lock is specified for each page.
- #3: For the number of logical files used by plug-ins, refer to the manuals included with the plug-ins.
- #4: Repeat and add this for the number of LOB columns and LOB attributes.
- #5: Total number of RDAREAs for the target tables, indexes, LOB columns, and LOB attributes.
(16) DELETE (temporary table, or LOCK TABLE specified and index key value no locking used#1)
(a) For a HiRDB single server configuration
[preprocessing]#2 + number of RDAREAs to be deleted#5 +
(number of deleted LOB data segments + number of segments storing the deleted LOB data)#4 + number of released data pages#6
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#3
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be deleted
- Add the following if routines are used for deletion:
- + number of routines used + 1
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#2
- Add the following if routines are used for deletion:
- + number of routines used + 1
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]#2
(d) For a HiRDB parallel server configuration (back-end server)
number of RDAREAs to be deleted#5 +
(number of deleted LOB data segments + number of segments storing the deleted LOB data)#4 + number of released data pages#6
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#3
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be deleted
- Add the following if routines are used for deletion:
- + number of routines used + 1
#1: If LOCK TABLE IN SHARE MODE is specified for a non-temporary table, the formula is the same as when LOCK TABLE is not specified.
#2: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
#3: For the number of logical files used by plug-ins, refer to the manuals included with the plug-ins.
#4: Repeat and add this for the number of LOB columns and LOB attributes.
#5: Total number of RDAREAs for the target indexes, LOB columns, and LOB attributes.
#6: Number of pages from which all data is deleted.
(17) DELETE (non-temporary table with LOCK TABLE not specified and index key value no locking used)
(a) For a HiRDB single server configuration
[preprocessing]#1 + number of RDAREAs to be deleted#2 + 1 + number of deleted rows#3 + number of VARCHAR, NVARCHAR, or MVARCHAR columns deleted that are 256 bytes or larger
number of branched rows
number of deleted rows + number of BINARY-type columns to be deleted that cannot be stored in one page
number of branched rows
number of deleted rows +
(number of deleted LOB data segments + number of segments storing the deleted LOB data)#4
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#5
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be deleted
- Add the following if routines are used for deletion:
- + number of routines used + 1
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#1
- Add the following if routines are used for deletion:
- + number of routines used + 1
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]#1
(d) For a HiRDB parallel server configuration (back-end server)
number of RDAREAs to be deleted#2 + 1 + number of deleted rows#3 + number of VARCHAR, NVARCHAR, or MVARCHAR columns deleted that are 256 bytes or larger
number of branched rows
number of deleted rows + number of BINARY-type columns that cannot be stored in one page
number of branched rows +
(number of deleted LOB data segments + number of segments storing the deleted LOB data)#4
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#5
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be deleted
- Add the following if routines are used for deletion:
- + number of routines used + 1
- #1: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
- #2: Total number of RDAREAs for the target tables, indexes, LOB columns, and LOB attributes.
- #3
- If there is a conditional expression that needs to retrieve data from another table, determine the number of hit retrieval rows for that table and add it to the number of deleted rows.
- If conditions are specified for an index definition column, determine the combined total of the rows that are retrieved based only on the conditions for each index. Then, use the number of hit retrieval rows as the number of deleted rows.
- Determine the number of hit retrieval rows after excluding conditions that use the columns of multiple tables and conditions that use functions. Then, use the number of hit retrieval rows as the number of deleted rows.
- Use the number of deleted pages if a lock is specified for each page. If a unique index is defined for the table, also add the value for the rows to be deleted.
- #4: Repeat and add this for the number of LOB columns and LOB attributes.
#5: For the number of logical files used by each plug-in, refer to the manual provided with the plug-in.
(18) DELETE (temporary table, or LOCK TABLE specified#6 and index key value no locking used)
(a) For a HiRDB single server configuration
[preprocessing]#1 + number of RDAREAs to be deleted#2 +
(number of deleted LOB data segments + number of segments storing the deleted LOB data)#3 + number of released data pages#4
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#5
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be deleted
- Add the following if routines are used for deletion:
- + number of routines used + 1
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#1
- Add the following if routines are used for deletion:
- + number of routines used + 1
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]#1
(d) For a HiRDB parallel server configuration (back-end server)
number of RDAREAs to be deleted#2 +
(number of deleted LOB data segments + number of segments storing the deleted LOB data)#3 + number of released data pages#4
- Add the following if a data-type plug-in or index-type plug-in is defined:
- + number of logical files used by the plug-in#5
- Add the following if the pd_inner_replica_control operand is specified:
- + number of RDAREAs to be deleted
- Add the following if routines are used for deletion:
- + number of routines used + 1
#1: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
#2: Total number of RDAREAs for the target indexes, LOB columns, and LOB attributes.
#3: Repeat and add this for the number of LOB columns and LOB attributes.
#4: Number of pages from which all data is deleted.
#5: For the number of logical files used by each plug-in, refer to the manual provided with the plug-in.
#6: If LOCK TABLE IN SHARE MODE is specified for a non-temporary table, the formula is the same as when LOCK TABLE is not specified.
(19) PURGE TABLE
(a) For a HiRDB single server configuration
[preprocessing]#1 + number of target RDAREAs#3 + 3 + number of table segments being used
2 +
((number of index segments being used
2) + 2)#2 +
(
number of segments for which LOB data is stored in HiRDB files
64,000
)#4
- Add the following if the pd_inner_replica_control operand is specified:
- + number of target RDAREAs
- Also add the following if USE is specified in the pd_check_pending operand or the operand is omitted, and if the target table is a referenced table:
- +
(number of target RDAREAs of the referencing table#3)#5
- Add the following if USE is specified in the pd_check_pending operand or the operand is omitted:
- + 4
- Also add the following if the target table is a referenced table:
- + 3 + number of table-storage RDAREAs for the target table + number of referencing tables that reference the target table
2 +
(1 + number of table-storage RDAREAs for referencing tables that reference the target table)#5 +
(number of target RDAREAs of the referencing tables#3 + 2)#5 - Also add the following if the target table is a partitioned table:
+ 1 + number of table-storage RDAREAs for the target table
- Also add the following if a referencing table that references the target table is a partitioned table:
+
(1 + number of table-storage RDAREAs for referencing tables that reference the target table)#5
- Also add the following if the target table is a referencing table or a table that defines a check constraint, and it does not include RDAREAs that apply the inner replica facility to the table-storage RDAREAs for the target table:
- + 1 + number of referential constraints defined in the target table + 1 + number of check constraints defined in the target table
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#1
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]#1
- Add the following if USE is specified in the pd_check_pending operand or the operand is omitted:
- + 4
- Also add the following if the target table is a referenced table:
- + 3 + number of table-storage RDAREAs for the target table + number of referencing tables that reference the target table
2 +
(1 + number of table-storage RDAREAs for referencing tables that reference the target table)#5 - Also add the following if the target table is a partitioned table:
+ 1 + number of table-storage RDAREAs for the target table
- Also add the following if a referencing table that references the target table is a partitioned table:
+
(1 + number of table-storage RDAREAs for referencing tables that reference the target table)#5
- Also add the following if the target table is a referencing table or a table that defines a check constraint, and it does not include RDAREAs that apply the inner replica facility to the table-storage RDAREAs for the target table:
- + 1 + number of referential constraints defined in the target table + 1 + number of check constraints defined in the target table
(d) For a HiRDB parallel server configuration (back-end server)
number of target RDAREAs#3 + 3 + number of table segments being used
2 +
((number of index segments being used
2) + 2)#2 +
(
number of segments for which LOB data is stored in HiRDB files
64,000
)#4
- Add the following if the pd_inner_replica_control operand is specified:
- + number of target RDAREAs
- Also add the following if USE is specified in the pd_check_pending operand or the operand is omitted, and if the target table is a referenced table:
- +
(number of target RDAREAs of a referencing table#3)#5
- Add the following if USE is specified in the pd_check_pending operand or the operand is omitted, and if the target table is a referenced table:
- +
(number of target RDAREAs of the referencing table#3 + 2)#5
#1: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
#2: Repeat and add this for the number of indexes.
#3: Total number of RDAREAs for the target tables, indexes, LOB columns, and LOB attributes.
#4: Repeat and add this for the number of HiRDB files for LOB RDAREAs of LOB columns and LOB attributes.
#5: Iteratively add the number of referencing tables that reference the target table.
(20) ASSIGN LIST statement (list creation from a base table)
(21) ASSIGN LIST statement (list creation from a list)
(a) For a HiRDB single server configuration
[preprocessing]# + 7 + number of RDAREAs storing the base table of the list + 4
- If an existing name is specified for the list to be created, add the following value:
- + number of RDAREAs storing the base table of the list before re-creation + 3 + number of segments using the list data before re-creation
(b) For a HiRDB parallel server configuration (front-end server)
[preprocessing]#
(c) For a HiRDB parallel server configuration (dictionary server)
[preprocessing]# + 7
- If an existing name is specified for the list to be created, add the following value:
- + number of RDAREAs storing the base table of the list before re-creation
(d) For a HiRDB parallel server configuration (back-end server)
number of RDAREAs storing the base table of the list + 4
- If an existing name is specified for the list to be created, add the following value:
- + 3 + number of segments using the list data before re-creation
#: For the number of lock requests in preprocessing, see (25) Number of lock requests in preprocessing.
(22) ASSIGN LIST statement (list name change)
(a) For a HiRDB single server configuration
7
- If an existing name is specified for the list to be created, add the following value:
- + number of RDAREAs storing the base table of the list before re-creation
(b) For a HiRDB parallel server configuration (dictionary server)
7
- If an existing name is specified for the list to be created, add the following value:
- + number of RDAREAs storing the base table of the list before re-creation
(23) DROP LIST statement (deletion with list name specification: DROP LIST ~)
(a) For a HiRDB single server configuration
7 + number of RDAREAs storing the base table of the list + 3 + number of segments using the list data
(b) For a HiRDB parallel server configuration (dictionary server)
7 + number of RDAREAs storing the base table of the list
(c) For a HiRDB parallel server configuration (back-end server)
3 + number of segments using the list data
(24) DROP LIST statement (deletion of all lists locally owned: DROP ALL LIST ~)
(a) For a HiRDB single server configuration
1 + number of RDAREAs for lists + number of deleted lists
2 + total number of segments using the deleted list data
(b) For a HiRDB parallel server configuration (dictionary server)
1
(c) For a HiRDB parallel server configuration (back-end server)
Number of RDAREAs for lists + number of deleted lists
2 + total number of segments using the deleted list data
(25) Number of lock requests in preprocessing