Admin: Using multiple schemas

Mon, 01 Jan 0001 00:00:00 +0000

Using a single schema is effective if there is only one database user or if a few users cooperate in sharing the database. In many cases, however, it makes sense to use additional schemas to allow users and their applications to create and access tables in separate namespaces. For example, using additional schemas allows:

Many users to access the database without interfering with one another.

Individual schemas can be configured to grant specific users access to the schema and its tables while restricting others.
Third-party applications to create tables that have the same name in different schemas, preventing table collisions.

Unlike other RDBMS, a schema in OpenText™ Analytics Database is not a collection of objects bound to one user.

Admin: Tables in schemas

Mon, 01 Jan 0001 00:00:00 +0000

You can create persistent and temporary tables, through CREATE TABLE and CREATE TEMPORARY TABLE, respectively.

For detailed information on both types, see Creating Tables and Creating temporary tables.

Persistent tables

CREATE TABLE creates a table in the database logical schema. For example:

CREATE TABLE vendor_dimension (
   vendor_key        INTEGER      NOT NULL PRIMARY KEY,
   vendor_name       VARCHAR(64),
   vendor_address    VARCHAR(64),
   vendor_city       VARCHAR(64),
   vendor_state      CHAR(2),
   vendor_region     VARCHAR(32),
   deal_size         INTEGER,
   last_deal_update  DATE

);

For detailed information, see Creating Tables.

Temporary tables

CREATE TEMPORARY TABLE creates a table whose data persists only during the current session. Temporary table data is never visible to other sessions.

Temporary tables can be used to divide complex query processing into multiple steps. Typically, a reporting tool holds intermediate results while reports are generated—for example, the tool first gets a result set, then queries the result set, and so on.

CREATE TEMPORARY TABLE can create tables at two scopes, global and local, through the keywords GLOBAL and LOCAL, respectively:

GLOBAL (default): The table definition is visible to all sessions. However, table data is session-scoped.
LOCAL: The table definition is visible only to the session in which it is created. When the session ends, the database automatically drops the table.

For detailed information, see Creating temporary tables.

OpenText Analytics Database 26.2.x – Designing a logical schema

Admin: Using multiple schemas

Admin: Tables in schemas

Persistent tables

Temporary tables