ER/Studio - Embarcadero Technologies Product Documentation

USING ER/STUDIO > DEVELOPING THE PHYSICAL MODEL
Name page/tab
Enter the name of auxiliary table and its owner.
• The table name is the fully-qualified name of the auxiliary table and must not be the same as any table, view,
alias, or synonym on the current server.
• The owner name is the name of the owner of the base table whose column you want to store in the auxiliary
table. This name is the authorization ID that qualifies the table name. If not specified, the DBS subsystem user
identifier for the connection used to create the database is used.
Base Table page/tab
• The base table identifier is the name of the base table whose column you want to store in the auxiliary table. The
auxiliary table is created to hold the data of a LOB column. The LOB column logically belongs to a regular table,
called the base table. However, because its data is too large to physically stored in the base table, the LOB
column data is physically stored in the auxiliary table. The base table identifier is also made up of owner name,
dot, table name. The drop-down list displays the name of all tables in the model that have tables defined with
BLOB or CLOB columns. The base table identifier is optional ER/Studio, but required for a valid CREATE AUX
TABLE SQL statement.
• You must have one auxiliary table per LOB column for a non-partitioned base table. However, if a LOB Column is
defined in a partitioned base table, then each LOB column must have a separate auxiliary table for each partition
in the base table. The drop-down list displays the name of all columns in the selected base table that are defined
as BLOB or CLOB datatypes. The LOB column name is optional ER/Studio, but required for a valid CREATE AUX
TABLE SQL statement.
• When creating an auxiliary table for a partitioned table, you can specify the number of the partition whose data
you want to store. This is only valid for LOB Columns defined in base tables stored in partitioned tablespaces.
Storage page/tab
• If you have any defined databases in the model, you can click the list and select the database where the auxiliary
table will be created. For more information, see Creating and Editing DataBases.
• Each auxiliary table must be defined in its own tablespace; i.e. you must have exactly one tablespace per
auxiliary table. The tablespace name can be qualified with the database name in which the tablespace resides.
Together the database.tablespace make up the tablespace identifier. The tablespace name is optional ER/Studio,
but required for a valid CREATE AUX TABLE SQL statement. For more information, see Creating and Editing
Tablespaces.
• Each auxiliary table requires a Unique Index.
Index Options page/tab
• Concurrent Copy: (COPY) If selected, concurrent copies of the index are allowed, which can increase index
availability by supporting index recovery.
• Do Not Close Dataset: (CLOSE) If selected, the index will not be closed when not in use. If not selected, the
dataset can be closed if it is not in use and the maximum number of open datasets is reached or exceeded.
• None: If selected, no USING clause is included in the CREATE INDEX statement.
• VCAT: (VCAT) If selected, allocates space for the index on a data set managed using the virtual catalog (VCAT)
whose name is specified next to this option, and the user manages the data sets required for the index. The VCAT
method is usually used for defining system catalogs. It requires that the VSAM dataset be pre-defined before the
index space is created.
EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 177