About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Last updated: Nov 26, 2024
You can use schemas to group virtual objects. A virtual object can belong to only one
schema. Use the
statement to create schemas.CREATE SCHEMA SQL
About this task
If a schema does not exist in your Data Virtualization service, you must create a schema
explicitly. Any user can create a schema with their own authorization name by using a
statement. For example, user with user ID CREATE
SCHEMA
can
create a private schema named dv_ibmid_1001
. To enable other users or roles to use the schema, dv_ibmid_1001
must grant CREATEIN, ALTERIN, or
DROPIN schema permissions to these users or roles. Additionally, granting these permissions to
PUBLIC enables the schema to be shared by all users.dv_ibmid_1001
Data Virtualization Managers can create schemas based on names other than the existing user’s authorization name. Data Virtualization Managers must grant appropriate permissions to other users or roles for them to use the schema to create virtual objects.
As Data Virtualization Manager, you can grant IMPLICIT_SCHEMA permissions to a user with the Data Virtualization Engineer role for each project. Data Virtualization Engineer can then create schemas to be used by other users in their project. When schemas are created by using the IMPLICIT_SCHEMA permission, PUBLIC is granted the CREATIN permission on these schemas.
Procedure
Was the topic helpful?
0/1000