Neoview Control Query Default (CQD) Reference Guide (R2.5)

9 Managing Catalogs and Schemas
This section describes these CQDs that are used for managing catalogs and schemas:
• “SCHEMA” (page 41)
• “PUBLISHING_ROLES” (page 41)
SCHEMA
Schema controlsCategory
Sets the default schema for the session.Description
SQL identifier
The default is the Default ROLE of the user.
Values
A SET SCHEMA statement, or a control query default SCHEMA statement, can be used to
override the default schema name.
Usage
It is a convenience so you do not have to type in 2 part names.Production usage
Not applicableImpact
AnyLevel
Alternately you can use the SET SCHEMA statement.
There is a CATALOG default also that allows you to set the catalog. For example, CATALOG
can be NEO, the system catalog, or MANAGEABILITY. Again it is a convenience to avoid
typing in long names.
Conflicts/Synergies
Not applicableAddressing the real
problem
Neoview Release 1.0Introduced in release
Not applicableDeprecated in release
PUBLISHING_ROLES
Schema controlsCategory
Specifies the name(s) of the role(s) which users must be a member of in order to use the
PUBLISH and UNPUBLISH commands to grant role level access to tables and views.
Description
A list of Roles separated by commas.
Values
This feature should be used only if it has been decided by Product Management that the
PUBLISH and UNPUBLISH support can be exposed to the customer.
Usage
UnknownProduction usage
Creates SYSTEM views and synonyms in users' schemas.Impact
This default can be set in the system defaults table and/or on a per session basis. However,
once it is set in a session it can’t be reset. It is recommended that it be set for every WMS
service level to prevent someone from assigning themselves this privilege once logged on.
Level
Use this CQD with these other defaults:
• DEFAULT_SCHEMA_NAMETYPE
• PUBLIC_SCHEMA_NAME
• DEFAULT_SCHEMA_ACCESS_ONLY
• CAT_ALLOW_MGR_PRIVS
• CAT_ALLOW_WGO_FOR_SCHEMA_GRANT
Conflicts/Synergies
Not applicableAddressing the real
problem
SCHEMA 41