Relational Design Center fully supports data access security by usercode to the row and column levels. This security enables you to control who can see specific tables, rows, and columns when using SQL interfaces. You can define security in Relational Design Center using SQL views.

Views are added to the SQL description through Relational Design Center. The SQL option in Relational Design Center is the default mode of operations. This mode enables the definition of views.

For more information about system security, refer to the MCP Security Overview and Implementation Guide.

SQL Security Constructs

If no explicit security is defined, access rights are as defined by the guard file specified for the physical database. If there is no guard file for the physical database, only the owner of the database has access rights.

Relational Design Center provides item and record subsystem-level security through the SQL constructs of views. When you enable SQL access to Enterprise Database Server databases using Relational Design Center, you can specify appropriate security using the views feature. You can define views and constraints for items mapped by default, as well as for items created with additional semantics.

The SQL database entities listed in the following table are referred to generically as items.

For SQL, the authorization identifier for the database is assumed to be the database name. For more information about SQL authorization identifiers, refer to the Query Processor Programming Guide.