Table of Contents
Advertisement
Considerations for CREATE VOLATILE TABLE
•
Volatile temporary tables are very similar to persistent tables, except that the life span of
the table is limited to the session that created the table. Once the session ends, the tables are
automatically dropped.
•
Volatile temporary table are closely linked to the session. Their namespace is unique across
multiple concurrent sessions, and therefore allow multiple sessions to use the same volatile
temporary table names simultaneously without any conflicts.
•
Volatile tables support creation of indexes.
•
Volatile tables are partitioned by the system.
•
Statistics are maintained for volatile tables much like for persistent tables.
•
Volatile tables can be created and accessed using one part name or two part names. However,
you must use the same name (one part or two part) for any further DDL or DML statements
on the created volatile table. See
Considerations for CREATE TABLE LIKE
The CREATE TABLE LIKE statement does not create views, owner information, or privileges
for the new table based on the source table. Privileges associated with a new table created by
using the LIKE specification are defined as if the new table is created explicitly by the current
user. If the source table has any unique or droppable primary key constraints, Neoview SQL
creates indexes for them on the target table. Other indexes on the source table are not created on
the target table.
Reserved Table Names
Table names prefixed by the name of a user metadata table are reserved. You cannot create tables
with such names. For example, you cannot create tables that are prefixed by these names:
•
HISTOGRAMS
•
HISTOGRAM_INTERVALS
•
MVS_TABLE_INFO_UMD
•
MVS_UMD
•
MVS_USED_UMD
Authorization and Availability Requirements
To create a table, you must own its schema.
Limits for Tables
You can create tables and indexes with rows that are 32,708 bytes in size and blocks that are 32K
bytes in size. The default block size for all create table and index operations is 32768 (32K) byte
block size (in all cases).
There are no tools provided for explicitly migrating an existing 4KB block size table to a 32KB
block size table. If you want a larger block size, a new table must be created and data copied
from the old table to the new table.
Table 2-1
describes the block size, the size available to Neoview SQL, and the size available to
the user.
Table 2-1 Maximum Row Sizes Available
Block size
4096
32768
74
SQL Statements
"Examples of CREATE TABLE" (page
Max row size available to SQL
4040
32712
78).
Max row size available to users
4036
32708
Advertisement
Table of Contents
