Neoview Database Administrator's Guide (R2.5)

Schemas

A schema ia a named collection of database objects (for example, tables, views, and indexes).

Each database object is described in only one schema, although an object can refer to objects

described in other schemas. A schema cannot contain other schemas. Each schema is described

in a catalog. The schema is the unit of ownership; all database objects in a schema are owned by

the schema owner.

Your Neoview platform is preconfigured with two schemas. For complete information about

creating and performing other actions on schemas, see the Neoview SQL Reference Manual and

the Neoview Command Interface (NCI) Guide.

Is used for...This schema

All tables that database administrators create in the database for end users, including

dimension and fact tables.

All tables created by end users using NCI or third-party tools that connect to ODBC

data sources.

USR

Tables

A table is a logical representation of data in a database in which a set of records is represented

as a sequence of rows, and the set of fields common to all the records is represented as a series

of columns. The intersection of a row and column represents the data value of a particular field

in a particular record. As a database object, a table defines data in columns and defines the

physical characteristics of the table.

Your Neoview platform is not preconfigured with tables, but you can create them immediately.

NOTE: Only user IDs that belong to the role that owns a schema can create tables in that schema.

For more information about roles and user IDs, see the Neoview User Management and Security

Administration Guide.

For complete information about creating and performing other actions on tables, see the Neoview

SQL Reference Manual and the Neoview Command Interface (NCI) Guide.

The owner of a schema can enable and disable Reorganize and Update Statistics for a table. For

more information, see Chapter 5 (page 25).

Indexes

An index provides an alternate access path (alternate key) to a table that differs from the primary

access path (clustering key) defined for the table at creation time. An index, stored in a

key-sequenced file, includes columns for the clustering key and the alternate key. Because your

Neoview platform is not preconfigured with tables, indexes are not configured, but you can

create them. For complete information about creating and performing other actions on indexes,

see the Neoview SQL Reference Manual and the Neoview Command Interface (NCI) Guide.

Views

A view is a logical table that contains no data. A view is derived by projecting a subset of the

columns, restricting a subset of the rows, or both, from one or more base tables or other views.

Because your Neoview platform is not preconfigured with tables, views are not configured, but

you can create them. For complete information about creating and performing other actions on

views, see the Neoview SQL Reference Manual and the Neoview Command Interface (NCI) Guide.

16 Getting Started