SQL/MP Installation and Management Guide

Adding, Altering, Removing, and Renaming
Database Objects
HP NonStop SQL/MP Installation and Management Guide—523353-004
7-3
Adding Tables
3. Enter the CREATE CATALOG statement, with or without the SECURE option.
4. Verify that the catalog’s security is set to allow SQL objects to be added and
accessed.
Adding Tables
Like adding new catalogs, adding new tables does not directly affect the existing
dictionary objects, except for collations. Creating a table is the first step in defining
SQL object dependencies, and no existing dependencies are affected. The new table
can, however, be dependent on one or more collations.
You can add new tables to new catalogs or to existing catalogs. To add a table, use the
CREATE TABLE statement.
If you are adding a new table to an existing application’s database, you should ensure
that the security and authority for the new table matches any existing security plan for
allowing access.
If any column of the new table corresponds to an existing column in another table, you
should define the new column with the same characteristics as the existing column.
A table added by a new version of SQL/MP software does not have the same version
as the software unless the table uses one of the new features in that software version.
For example, a table added by version 310 software is not a version 310 table unless it
uses a feature not available in an older version of SQL/MP software. For more
information, see the SQL/MP Version Management Guide.
To add a table, follow these steps:
1. Start an SQLCI session. Enter a LOG command to initiate a log file for the
statements and commands entered in this session. Keep the log for your records.
2. Query the CATALOGS table of the system catalog or use the FILEINFO command
to check that the target catalog already exists. The catalog must exist to create a
table.
3. Query the TABLES table of the catalog to check that the table name is available.
4. Plan the column definitions, checking that the data type of any column that might
be necessary for join or predicate search operations matches the joined column.
5. Make sure that collations exist before you refer to them in column definitions. If a
collation to be used by a column does not exist, create the collation as explained
under Creating Collations on page 5-55.
6. Enter the CREATE TABLE statement, or put the statement text into an EDIT file
and enter an OBEY command to run the statement from the file.
7. Alter the security and ownership of the new table, if necessary.
8. For an audited table, make a TMF online dump. For a partitioned audited table,
make an online dump of each partition.