Appendix E.2 Data manipulation SQLs

Organization of this subsection
(1) SELECT (LOCK TABLE not specified, WITHOUT LOCK not specified)
(2) SELECT (LOCK TABLE not specified, WITHOUT LOCK WAIT specified)
(3) SELECT (LOCK TABLE not specified, WITHOUT LOCK NOWAIT specified)
(4) SELECT (LOCK TABLE specified1)
(5) INSERT (INSERT to VALUES clauses specified, and LOCK TABLE not specified)
(6) INSERT (INSERT to VALUES clauses specified, LOCK TABLE specified1)
(7) INSERT (INSERT to SELECT clauses specified)
(8) INSERT (INSERT to VALUES clauses specified, LOCK TABLE not specified, index key value no locking used)
(9) INSERT (INSERT to VALUES clauses specified, LOCK TABLE specified, index key value no locking used)
(10) INSERT (INSERT to SELECT clauses specified, index key value no locking used)
(11) UPDATE (LOCK TABLE not specified)
(12) UPDATE (LOCK TABLE specified1)
(13) UPDATE (LOCK TABLE not specified, index key value no locking used)
(14) UPDATE (LOCK TABLE specified, index key value no locking used)
(15) DELETE (LOCK TABLE not specified)
(16) DELETE (LOCK TABLE specified1)
(17) DELETE (LOCK TABLE not specified, index key value no locking used)
(18) DELETE (LOCK TABLE specified, 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 (LOCK TABLE not specified, WITHOUT LOCK not specified)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]1 + number of RDAREAs for table to be retrieved + number of tables + number of rows with retrieval hit3 + number of RDAREAs storing the indexes used2 + number of index keys used in retrieval5
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-in4
The following should be noted if table data is retrieved via a list:
  • The number of lock requests in preprocessing in the formula should be determined by applying it to the base table of the list.
  • The number of RDAREAs storing the tables to be retrieved and the number of tables in the formula should be determined for the base table of the list.
  • The following value must be added:
+ 1
Add the following if routines are used for retrieval:
+ number of routines used
HiRDB/Parallel ServerFront-end server and Dictionary server[preprocessing]1
If table data is retrieved via a list, the number of lock requests in preprocessing in the formula should be determined by applying it to the base table of the list.
Add the following if routines are used for retrieval:
+ number of routines used
Back-end serverNumber of RDAREAs for table to be retrieved + number of tables + number of rows with retrieval hit3 + number of RDAREAs storing the indexes used2 + number of indexes used in retrieval5
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-in4
The following should be noted if table data is retrieved via a list:
  • The number of RDAREAs storing the tables to be retrieved and the number of tables in the formula should be determined for the base table of the list.
  • The following value must be added:
+ 1
Add the following if routines are used for retrieval:
+ number of routines used
1 For the number of lock requests in preprocessing, see (25).
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 selection 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 individual indexes.
  • Determine the number of hit selection rows after excluding conditions that use the columns of multiple tables and conditions that use functions.
  • Use the number of hit selection 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 (LOCK TABLE not specified, WITHOUT LOCK WAIT specified)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]1 + number of RDAREAs to be retrieved + number of tables + 1 + number of RDAREAs for index used2
+ number of index keys used in retrieval4
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-in3
The following should be noted if table data is retrieved via a list:
  • The number of lock requests in preprocessing in the formula should be determined by applying it to the base table of the list.
  • The number of RDAREAs storing the tables to be retrieved and the number of tables in the formula should be determined for the base table of the list.
  • The following value must be added:
+ 1
Add the following if routines are used for retrieval:
+ number of routines used
HiRDB/Parallel ServerFront-end server and Dictionary server[preprocessing]1
If table data is retrieved via a list, the number of lock requests in preprocessing in the formula should be determined by applying it to the base table of the list.
Add the following if routines are used for retrieval:
+ number of routines used
Back-end serverNumber of RDAREAs to be retrieved + number of tables + 2 + number of RDAREAs for index used2
+ number of index keys used in retrieval4
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-in3
The following should be noted if table data is retrieved via a list:
  • The number of RDAREAs storing the tables to be retrieved and the number of tables in the formula should be determined for the base table of the list.
  • The following value must be added:
+ 1
Add the following if routines are used for retrieval:
+ number of routines used

1 For the number of lock requests in preprocessing, see (25).

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 (LOCK TABLE not specified, WITHOUT LOCK NOWAIT specified)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]1 + number of RDAREAs to be retrieved + number of tables + number of RDAREAs storing indexes used2
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-in3
The following should be noted if table data is retrieved via a list:
  • The number of lock requests in preprocessing in the formula should be determined by applying it to the base table of the list.
  • The number of RDAREAs storing the tables to be retrieved and the number of tables in the formula should be determined for the base table of the list.
  • The following value must be added:
+ 1
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 retrieval:
+ number of routines used
HiRDB/Parallel ServerFront-end server and Dictionary server[preprocessing]1
If table data is retrieved via a list, the number of lock requests in preprocessing in the formula should be determined by applying it to the base table of the list.
Add the following if routines are used for retrieval:
+ number of routines used
Back-end serverNumber of RDAREAs to be retrieved + number of tables + number of RDAREAs storing indexes used2
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-in3
The following should be noted if table data is retrieved via a list:
  • The number of RDAREAs storing the tables to be retrieved and the number of tables in the formula should be determined for the base table of the list.
  • The following value must be added:
+ 1
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 retrieval:
+ number of routines used

1 For the number of lock requests in preprocessing, see (25).

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 (LOCK TABLE specified1)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]2 + number of RDAREAs to be retrieved + number of RDAREAs storing 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-in3
The following should be noted if table data is retrieved via a list:
  • The number of lock requests in preprocessing in the formula should be determined by applying it to the base table of the list.
  • The number of RDAREAs storing the tables to be retrieved and the number of tables in the formula should be determined for the base table of the list.
  • The following value must be added:
+ 1
Add the following if routines are used for retrieval:
+ number of routines used
HiRDB/Parallel ServerFront-end server and Dictionary server[preprocessing]2
If table data is retrieved via a list, the number of lock requests in preprocessing in the formula should be determined by applying it to the base table of the list.
Add the following if routines are used for retrieval:
+ number of routines used
Back-end serverNumber of RDAREAs to be retrieved + number of RDAREAs storing 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-in3
The following should be noted if table data is retrieved via a list:
  • The number of RDAREAs storing the tables to be retrieved and the number of tables in the formula should be determined for the base table of the list.
  • The following value must be added:
+ 1
Add the following if routines are used for retrieval:
+ number of routines used

1 If LOCK TABLE IN SHARE MODE is specified for SELECT with FOR UPDATE specified, the same formula should be used as when LOCK TABLE in not specified.

2 For the number of lock requests in preprocessing, see (25).

3 For the number of logical files used by plug-ins, refer to the manuals included with the plug-ins.

(5) INSERT (INSERT to VALUES clauses specified, and LOCK TABLE not specified)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]1 + 5 + number of RDAREAs to be inserted3 + number of inserted VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger[Figure] number of branched rows + number of inserted BINARY-type columns that cannot be stored in one page[Figure] 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 plug-ins2
Add the following if routines are used for insertion:
+ number of routines used
HiRDB/Parallel ServerFront-end server and Dictionary server[preprocessing]1
Add the following if routines are used for insertion:
+ number of routines used
Back-end server5 + number of RDAREAs to be inserted3 + number of inserted VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger[Figure] number of branched rows + number of inserted BINARY-type columns that cannot be stored in one page[Figure] 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 plug-ins2
Add the following if routines are used for insertion:
+ number of routines used

1 For the number of lock requests in preprocessing, see (25).

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 (INSERT to VALUES clauses specified, LOCK TABLE specified1)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]2 + 1 + number of RDAREAs to be inserted4
Add the following if a data-type plug-in or index-type plug-in is defined:
+ number of logical files used by plug-in*3
Add the following if routines are used for insertion:
+ number of routines used
HiRDB/Parallel ServerFront-end server and Dictionary server[preprocessing]2
Add the following if routines are used for insertion:
+ number of routines used
Back-end server1 + 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 plug-ins*3
Add the following if routines are used for insertion:
+ number of routines used

1 If LOCK TABLE IN SHARE MODE is specified, the same formula should be used as when LOCK TABLE in not specified.

2 For the number of lock requests in preprocessing, see (25).

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)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]1 + 5 + number of RDAREAs to be inserted5 + 4 + number of inserted rows2 + number of inserted VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger[Figure] number of inserted rows2[Figure] number of branched rows + number of inserted BINARY-type columns that cannot be stored in one page[Figure] number of inserted rows2[Figure] number of branched rows + number of inserted rows[Figure] number of indexes + 1 + number of RDAREAs to be retrieved5 + number of tables to be retrieved + number of hit selection rows3
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 inserted4 + number of logical files used by the plug-ins used for retrieval4
Add the following if routines are used for insertion:
+ number of routines used
HiRDB/Parallel ServerFront-end server and Dictionary server[preprocessing]1
Add the following if routines are used for insertion:
+ number of routines used
Back-end server4 + number of RDAREAs to be inserted5 + number of inserted rows2 + number of inserted VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger[Figure] number of inserted rows[Figure] number of inserted BINARY-type columns that cannot be stored in one page[Figure] number of inserted rows[Figure] number of branched rows + number of inserted rows[Figure] number of indexes + 1 + number of RDAREAs to be retrieved5 + number of tables to be retrieved + number of hit selection rows3
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 inserted4 + number of logical files used by the plug-ins used for retrieval4
Add the following if routines are used for insertion:
+ number of routines used
1 For the number of lock requests in preprocessing, see (25).
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 selection 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 individual indexes.
  • Determine the number of hit selection rows after excluding conditions that use the columns of multiple tables and conditions that use functions.
  • Use the number of hit selection 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.

(8) INSERT (INSERT to VALUES clauses specified, LOCK TABLE not specified, index key value no locking used)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]1 + 5 + number of RDAREAs to be inserted2 + number of inserted VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger[Figure] number of branched rows + number of inserted BINARY-type columns that cannot be stored in one page[Figure] number of branched rows + number of indexes + 1
Add the following if a data-type plug-in or index-type plug-in is defined:
+ number of logical files used by plug-ins3
Add the following if routines are used for insertion:
+ number of routines used
HiRDB/Parallel Server

1 For the number of lock requests in preprocessing, see (25).

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 (INSERT to VALUES clauses specified, LOCK TABLE specified, index key value no locking used)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]1 + 1 + number of RDAREAs to be inserted2
Add the following if a data-type plug-in or index-type plug-in is defined:
+ number of logical files used by plug-ins3
Add the following if routines are used for insertion:
+ number of routines used
HiRDB/Parallel Server

1 For the number of lock requests in preprocessing, see (25).

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.

(10) INSERT (INSERT to SELECT clauses specified, index key value no locking used)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]1 + number of RDAREAs to be inserted2 + 4 + number of inserted rows3 + number of inserted VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger[Figure] number of inserted rows[Figure] number of branched rows + number of inserted BINARY-type columns that cannot be stored in one page[Figure] number of inserted rows[Figure] number of branched rows + number of indexes + 1 + number of RDAREAs to be retrieved2 + number of tables to be retrieved + number of hit selection rows4
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 inserted5 + number of logical files used by the plug-ins used for retrieval5
Add the following if routines are used for insertion:
+ number of routines used
HiRDB/Parallel Server
1 For the number of lock requests in preprocessing, see (25).
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 selection 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 individual indexes.
  • Determine the number of hit selection rows after excluding conditions that use the columns of multiple tables and conditions that use functions.
  • Use the number of hit selection 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.

(11) UPDATE (LOCK TABLE not specified)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]1 + number of RDAREAs to be updated5 + 4 + number of updated rows2 + number of pre-update VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger[Figure] number of pre-update rows[Figure] number of branched rows before update + number of post-update VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger[Figure] number of post-update rows[Figure] number of branched rows after update + number of pre-update BINARY-type columns that cannot be stored in one page[Figure] number of pre-update rows[Figure] number of branched rows before update + number of post-update BINARY-type columns that cannot be stored in one page[Figure] number of post-update rows[Figure] number of branched rows after update + number of indexes to be updated[Figure] 2 [Figure] number of updated rows + [Figure] (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-ins3
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
HiRDB/Parallel ServerFront-end server and Dictionary server[preprocessing]1
Add the following if routines are used for updating:
+ number of routines used
Back-end servernumber of RDAREAs to be updated5 + 4 + number of updated rows2 + number of pre-update VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger[Figure] number of pre-update rows[Figure] number of branched rows before update + number of post-update VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger[Figure] number of post-update rows[Figure] number of branched rows after update + number of pre-update BINARY-type columns that cannot be stored in one page[Figure] number of pre-update rows[Figure] number of branched rows before update + number of post-update BINARY-type columns that cannot be stored in one page[Figure] number of post-update rows[Figure] number of branched rows after update + number of indexes to be updated[Figure] 2 [Figure] number of updated rows + [Figure] (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-ins3
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 For the number of lock requests in preprocessing, see (25).
2
  • If there is a conditional expression that needs to retrieve data from another table, determine the number of hit selection 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 individual indexes. Furthermore, use the number of hit selection rows as the number of updated rows.
  • Determine the number of hit selection rows after excluding conditions that use the columns of multiple tables and conditions that use functions. Furthermore, use the number of hit selection 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 (LOCK TABLE specified1)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]2 + number of RDAREAs to be updated5 + 1 + [Figure] (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-ins3
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
HiRDB/Parallel ServerFront-end server and Dictionary server[preprocessing]2
Add the following if routines are used for updating:
+ number of routines used
Back-end servernumber of RDAREAs to be updated5 + 1 + [Figure] (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-ins3
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 If LOCK TABLE IN SHARE MODE is used, use the same formula as that used when there is no LOCK TABLE.

2 For the number of lock requests in preprocessing, see (25).

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 (LOCK TABLE not specified, index key value no locking used)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]1 + number of RDAREAs to be updated2 + 4 + number of updated rows3 + number of pre-update VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger[Figure] number of pre-update rows[Figure] number of branched rows before update + number of post-update VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger[Figure] number of post-update rows[Figure] number of branched rows after update + number of pre-update BINARY-type columns that cannot be stored in one page[Figure] number of pre-update rows[Figure] number of branched rows before update + number of post-update BINARY-type columns that cannot be stored in one page[Figure] number of post-update rows[Figure] number of branched rows after update + [Figure] (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 plug-ins5
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
HiRDB/Parallel Server
1 For the number of lock requests in preprocessing, see (25).
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 selection 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 individual indexes. Furthermore, use the number of hit selection rows as the number of updated rows.
  • Determine the number of hit selection rows after excluding conditions that use the columns of multiple tables and conditions that use functions. Furthermore, use the number of hit selection 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 (LOCK TABLE specified, index key value no locking used)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]1 + number of RDAREAs to be updated2 + 1 + [Figure] (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 plug-ins4
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
HiRDB/Parallel Server

1 For the number of lock requests in preprocessing, see (25).

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.

(15) DELETE (LOCK TABLE not specified)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]1 + number of RDAREAs to be deleted5 + 1 + number of deleted rows2 + number of VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger[Figure] number of branched rows + number of BINARY-type columns that cannot be stored in one page[Figure] number of branched rows + number of indexes[Figure] number of deleted rows + [Figure] (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-ins3
Add the following if routines are used for deletion:
+ number of routines used
HiRDB/Parallel ServerFront-end server and Dictionary server[preprocessing]1
Add the following if routines are used for deletion:
+ number of routines used
Back-end servernumber of RDAREAs to be deleted5 + 1 + number of deleted rows2 + number of VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger[Figure] number of branched rows + number of BINARY-type columns that cannot be stored in one page[Figure] number of branched rows + number of indexes[Figure] number of deleted rows + [Figure] (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-ins3
Add the following if routines are used for deletion:
+ number of routines used
1 For the number of lock requests in preprocessing, see (25).
2
  • If there is a conditional expression that needs to retrieve data from another table, determine the number of hit selection 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 individual indexes. Furthermore, use the number of hit selection rows as the number of deleted rows.
  • Determine the number of hit selection rows after excluding conditions that use the columns of multiple tables and conditions that use functions. Furthermore, use the number of hit selection 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 (LOCK TABLE specified1)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]2 + number of RDAREAs to be deleted5 + [Figure] (number of segments storing the deleted LOB data)4 + number of released data pages6
Add the following if a data-type plug-in or index-type plug-in is defined:
+ number of logical files used by the plug-ins3
Add the following if routines are used for deletion:
+ number of routines used
HiRDB/Parallel ServerFront-end server and Dictionary server[preprocessing]2
Add the following if routines are used for deletion:
+ number of routines used
Back-end servernumber of RDAREAs to be deleted5 + [Figure] (number of segments storing the deleted LOB data4 + number of released data pages6
Add the following if a data-type plug-in or index-type plug-in is defined:
+ number of logical files used by the plug-ins3
Add the following if routines are used for deletion:
+ number of routines used

1 If LOCK TABLE IN SHARE MODE is specified, the same formula should be used as when LOCK TABLE in not specified.

2 For the number of lock requests in preprocessing, see (25).

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 (LOCK TABLE not specified, index key value no locking used)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]1 + number of RDAREAs to be deleted2 + 1 + number of deleted rows3 + number of VARCHAR, NVARCHAR, or MVARCHAR columns that are 256 bytes or larger[Figure] number of branched rows + number of BINARY-type columns that cannot be stored in one page[Figure] number of branched rows + [Figure] (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 plug-ins5
Add the following if routines are used for deletion:
+ number of routines used
HiRDB/Parallel Server
1 For the number of lock requests in preprocessing, see (25).
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 selection 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 individual indexes. Furthermore, use the number of hit selection rows as the number of deleted rows.
  • Determine the number of hit selection rows after excluding conditions that use the columns of multiple tables and conditions that use functions. Furthermore, use the number of hit selection 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 (LOCK TABLE specified, index key value no locking used)

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]1 + number of RDAREAs to be deleted2 + [Figure] (number of segments storing the deleted LOB data)3 + number of released data pages4
Add the following if a data-type plug-in or index-type plug-in is defined:
+ number of logical files used by plug-ins5
Add the following if routines are used for deletion:
+ number of routines used
HiRDB/Parallel Server

1 For the number of lock requests in preprocessing, see (25).

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.

(19) PURGE TABLE

ConditionNumber of lock requests
HiRDB/Single Server[preprocessing]1 + number of target RDAREAs3 + 3 + number of table segments being used + [Figure] (number of index segments being used + 2)2 + [Figure] ([Figure] number of segments for which LOB data is stored in HiRDB file[Figure] 64000 [Figure])4
HiRDB/Parallel ServerFront-end server and Dictionary server[preprocessing]1
Back-end servernumber of target RDAREAs3 + 3 + number of table segments + [Figure] (number of index segments being used + 2)2 + [Figure] ([Figure] number of segments for which LOB data is stored in HiRDB file[Figure] 64000[Figure])4

1 For the number of lock requests in preprocessing, see (25).

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.

(20) ASSIGN LIST statement (list creation from a base table)

ConditionNumber of lock requests
HiRDB/Single Servernumber of base table SELECT lock requests1 + 7 + 2
Add the following value if an existing list is specified as the name of the list to be created:
+ number of RDAREAs for the base table of the list before re-creation + 3 + number of data segments of the list before re-creation
HiRDB/Parallel ServerFront-end server[preprocessing]2
Dictionary serverpreprocessing2 + 7
Add the following value if an existing list is specified as the name of the list to be created:
+ number of RDAREAs for the base table of the list before re-creation
Back-end servernumber of base table SELECT lock requests1 + 2
Add the following value if an existing list is specified as the name of the list to be created:
+ 3 + number of data segments of the list before re-creation

1 For the number of base table SELECT lock requests, choose from the SELECT statements in (1) through (4) the statement that satisfies the condition of the base table and refer to it.

2 For the number of lock requests in preprocessing, see (25).

(21) ASSIGN LIST statement (list creation from a list)

ConditionNumber of lock requests
HiRDB/Single Server[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
HiRDB/Parallel ServerFront-end server[preprocessing]*
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
Back-end servernumber 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).

(22) ASSIGN LIST statement (list name change)

ConditionNumber of lock requests
HiRDB/Single Server7
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
HiRDB/Parallel Server (Dictionary server)

(23) DROP LIST statement (deletion with list name specification: DROP LIST [Figure])

ConditionNumber of lock requests
HiRDB/Single Server7 + number of RDAREAs storing the base table of the list + 3 + number of segments using the list data
HiRDB/Parallel ServerDictionary server7 + number of RDAREAs storing the base table of the list
Back-end server3 + number of segments using the list data

(24) DROP LIST statement (deletion of all lists locally owned: DROP ALL LIST [Figure])

ConditionNumber of lock requests
HiRDB/Single Server1 + number of RDAREAs for lists + number of deleted lists [Figure]2 + total number of segments using the deleted list data
HiRDB/Parallel ServerDictionary server1
Back-end serverNumber of RDAREAs for lists + number of deleted lists [Figure]2 + total number of segments using the deleted list data

(25) Number of lock requests in preprocessing

ConditionNumber of lock requests
HiRDB/Single Server1 + number of tables used + number of view tables used + [Figure]1(2 + number of columns[Figure] 2 + number of indexes[Figure] 2 + number of table partitions[Figure] 4 + [Figure]2(number of partitioning indexes[Figure] 2) + 2) + 13
Add the following if a user-defined type or function is used:
+ 1
Add the following (for each table) if optimization information is collected:
+ 1 + number of columns for which optimization information is created[Figure] 4 + 1
Add the following (for each view table) if view tables are used:
+ [Figure] (number of columns[Figure] 2 + 4 + number of columns comprising the view table + 2)
Add the following if LOB columns are defined:
+ number of LOB columns[Figure] 2 + number of table partitions
Add the following if user-defined type columns are defined:
number of user-defined type columns + [Figure] (4 + number of attributes[Figure] 2)
Add the following if LOB attributes are used:
+ number of LOB attributes[Figure] 2 + number of table partitions
Add the following if a higher-order type is used:
+ 2
Add the following for each function used if functions are used:
+ [Figure] (2 + number of functions with the same name and parameter configuration[Figure] 2 + number of parameters[Figure] 2)
Add the following for each plug-in used if plug-ins are used:
+ [Figure] (2 + number of parameters[Figure] 2) + 3 + number of contexts[Figure] 4 + 2
Add the following if routines are used:
+ number of routines used
HiRDB/Parallel ServerFront-end server1 + number of tables used + number of view tables used
Add the following if a user-defined type or function is used:
+ 1
Add the following if routines are used:
+ number of routines used
Dictionary server[Figure]1(2 + number of columns[Figure] 2 + number of indexes[Figure] 2 + number of table partitions[Figure] 4 + [Figure]2(number of partitioning indexes[Figure] 2) + 2) + 13
Add the following (for each table) if optimization information is collected:
+ 1 + number of columns for which optimization information is created[Figure] 4 + 1
Add the following (for each view table) if view tables are used:
+ [Figure] (number of columns[Figure] 2 + 4 + number of columns comprising the view table + 2)
Add the following if LOB columns are defined:
+ number of LOB columns[Figure] 2 + number of table partitions
Add the following for each user-defined type column if user-defined type columns are defined:
+ [Figure] (4 + number of attributes[Figure] 2)
Add the following if LOB attributes are used:
+ number of LOB attributes[Figure] 2 + number of table partitions
Add the following if a higher-order type is used:
+ 2
Add the following for each function used if functions are used:
+ [Figure] (2 + number of functions with the same name and parameter configuration[Figure] 2 + number of parameters[Figure] 2)
Add the following for each plug-in used if plug-ins are used:
+ [Figure] (2 + number of parameters[Figure] 2) + 3 + number of contexts[Figure] 4 + 2
Add the following if routines are used:
+ number of routines used

1 Summarize this for each table.

2 Summarize this for each partitioning index inside the table.