You can import a relational schema of an Enterprise Database Server database or obtain a schema of an SQL database that has already been created. Consider the following factors when importing a relational schema:
-
The database name you enter should include the location of the Enterprise Database Server control file. You should enter the database name in the format (<usercode>)<database name> ON <pack name>.
-
To import a logical database, enter the database name in the format <logical database name> OF (<usercode>)<database name> ON <pack name>.
-
The database description file name is optional. If you decide not to specify a database description file, the Relational Design Center assumes that the description file is located under the usercode and pack name specified in the Database Name box.
If you do not specify a usercode and pack in the Database Name box, the Relational Design Center assumes the description file is located under the usercode and pack of the person attempting to access the database.
-
To enable SQL queries to update the database, select the Read-only access control option.
-
To authenticate log-in credentials using your ClearPath MCP usercode and password, select the MCP option in the Authentication list and type your log-in credentials.
-
To authenticate log-in credentials using Kerberos credentials, select the Kerberos option in the Authentication list.
To encrypt your Kerberos credentials, select the Encryption option in the Encryption list.
-
The usercode can consist of usercode, accesscode, and chargecode combinations as shown in the following syntax. Accesscode and chargecode requirements are defined by your system administrator.
──<usercode˃─┬──────────────────────────────────────┬───────────────────┤
├─ /<accesscode˃───────────────────────┤
├─ /<chargecode˃───────────────────────┤
└─ /<accesscode˃/<chargecode˃──────────┘The password can consist of a password and an optional accesscode password as shown in the following syntax:
──<password˃──┬───────────────────────────┬─────────────────────────────┤
└─ /<accesscode password˃───┘Perform the following steps to create a relational schema of an Enterprise Database Server database or to import a schema of an SQL database that has already been created:
-
From the tree view, right-click the server that contains the database you want to map, and click Import Relational Schema.
The Import Relational Schema dialog box appears.
-
Enter the appropriate information in the text boxes.
-
Click Import.
The Relational Design Center attempts to create a relational schema of the database.
If the create operation is successful, the database is added to the tree view along with its properties in the properties view.
The results of the operation appear in the output view.
When you exit the Relational Design Center, the tree view structure is preserved. After you open the database, the Relational Design Center checks the database timestamp to determine whether an update mapping is required. If a mapping is required, the mapping is automatically updated. If the Relational Design Center determines that an update mapping is not required, the data items for the database are loaded into the tree view.
| Note: | Query Processor does not support Enterprise Database Server items that use the DATAENCRYPT or DATAMASK options. Structures that include these options cannot be mapped to the SQL view.For more information on the DATAENCRYPT and DATAMASK options, see the Data and Structure Definition Language (DASDL) Programming Reference Manual. |
