ER/Studio - Embarcadero Technologies Product Documentation
ER/Studio - Embarcadero Technologies Product Documentation ER/Studio - Embarcadero Technologies Product Documentation
USING ER/STUDIO > COMMON TASKS Page 4 For each operation, select the submodels you want to synchronize with the target model. The available operations (update, delete) depend on the submodel chosen. If this is a frequently updated submodel, you may want to save all the wizard settings in a Quick Launch file. The file will load your selections when you next use the utility if you select it upon launching the utility. You can load the quick launch file and make changes to it and then save the changes if you want. Notes • To make changes to both the source and target models, run the utility twice, reversing the source and target the second time you run the utility. • The available operations (update, delete) will depend on the submodel chosen and the differences that exist between the source and target submodels. For example, if the source contains updates not reflected in the target, then the update operation will be available. Copying a Database Object to a Submodel (Apply to Submodel) You can replicate database objects by copying the object and then pasting it to each submodel individually or you can use the Apply to Submodel function to paste an object into multiple submodels within the same model simultaneously. 1 In either the Data Model Explorer or the Data Model Window, right-click the object you want to copy to one or more submodels in the active model and then click Apply to Submodel. 2 In the Apply to Submodel dialog, individually select the submodels you want to copy the object to, or select the model to copy the object to the main model and all submodels of the active model. NOTE: In the Apply to Submodel dialog, clicking Place New Object Near Existing Objects prevents the new object from being placed randomly in the Data Model Window. This can be important when working with large models and submodels. Establishing Database Security Define and establish database security to, for example, inform data model reviewers and database administrators of the security required for data model objects when these objects are implemented on a DBMS. This section includes the following topics: • Creating and Editing Database Users • Creating and Editing Database Roles • Associating Database Users with New Database Roles • Associating Database Roles with New Database Users • Changing Database Roles Associated with Existing Database Users • Changing Database Users Associated with Existing Database Roles • Granting and Revoking Permissions to Modify Database Objects Creating and Editing Database Users Granting database access, authorities, and privileges to users and groups is one of the most important ways to ensure data security. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 80
USING ER/STUDIO > COMMON TASKS In conjunction with database roles, users and the permissions you grant them enable you to manage the permissions logical model users have to insert, select, update, delete, alter, or reference entities, tables, and views in the logical database. In addition to being supported by tables and views in the physical data model, depending on the database platform, users also can be applied to specific physical models to manage system privileges such as those required to backup databases and logs, or to create databases, defaults, procedures, rules, tables, and views. The system privileges available are database dependent and display on page 2 of the User Wizard and User Editor. Database users are supported by the logical data model and are also supported by physical data models for the following platforms: • IBM DB2 for LUW 5.x, 6.x, 7.x, 8.x, 9.x • IBM DB2 for OS/390 5.x and 6.x, and DB2 for z/OS 7.x, 8.x, 9.x • Microsoft SQL Server 4.x, 6.x, 7.x, 2000, 2005 • Oracle 7.x, 8.x, 9i, 10g, 11g • Sybase ASE 11.0, 11.5, 11.9, 12.0, 12.5, 15 NOTE: The User Wizard and User Editor share the same options, except for Attachment Bindings options which are present only in the editor. 1 In the Data Model Window, expand the Main Model of the Logical model, or of a physical model for which database users are supported, right-click the Users node, and then click New Database User. 2 In the User Wizard, assign the permissions desired, and then click Finish. The following describe options that require additional explanation. NOTE: Options and permissions available are platform-dependant. General page/tab • User Name: The restrictions for the number of character permitted when defining user and group names is dependant on the database platform. • Is Group: Members of a user group automatically inherit group privileges. Privileges granted to a user override the privileges associated with any groups the user is a member of, and are retained if the user is later removed from the groups. Explicit privileges granted to a user must be explicitly revoked. • Password: When selected, specifies that the user is a local user who must specify a password when accessing the database. • Externally: When selected, specifies that the user is an external user who must be authorized by an external service, such as an operating system or third-party service, to access the database. • Globally: When selected, specifies that the user is a global user who must be authorized to use the database by the enterprise directory service or at login. • Add: When clicked, the Select Roles dialog appears where you can select the roles to assign to the user. Hold CTRL-Shift to select multiple roles. If you have not previously defined a role, the list will be empty. • Tablespace Quota: On some physical models, you can define tablespace usage parameters (in units of 10KB). This will limit a user’s ability to grow a tablespace, but should not be used instead of designed range limits. System Privileges page/tab Clicking the column name selects the entire column. Control-click to select multiple objects. The permissions available are dependant on the physical platform selected. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 81
- Page 29 and 30: ER/STUDIO OVERVIEW > CONFIGURING AN
- Page 31 and 32: ER/STUDIO OVERVIEW > CONFIGURING AN
- Page 33 and 34: ER/STUDIO OVERVIEW > CONFIGURING AN
- Page 35 and 36: ER/STUDIO OVERVIEW > DATA MODELING
- Page 37 and 38: ER/STUDIO OVERVIEW > DEVELOPING A D
- Page 39 and 40: Using ER/Studio This section includ
- Page 41 and 42: USING ER/STUDIO > CREATING AND WORK
- Page 43 and 44: USING ER/STUDIO > CREATING AND WORK
- Page 45 and 46: USING ER/STUDIO > CREATING AND WORK
- Page 47 and 48: USING ER/STUDIO > CREATING AND WORK
- Page 49 and 50: USING ER/STUDIO > CREATING AND WORK
- Page 51 and 52: USING ER/STUDIO > CREATING AND WORK
- Page 53 and 54: USING ER/STUDIO > CREATING AND WORK
- Page 55 and 56: USING ER/STUDIO > CREATING AND WORK
- Page 57 and 58: USING ER/STUDIO > CREATING AND WORK
- Page 59 and 60: USING ER/STUDIO > CREATING AND WORK
- Page 61 and 62: USING ER/STUDIO > CREATING AND WORK
- Page 63 and 64: USING ER/STUDIO > BEST PRACTICES 8
- Page 65 and 66: USING ER/STUDIO > COMMON TASKS Comm
- Page 67 and 68: USING ER/STUDIO > COMMON TASKS Movi
- Page 69 and 70: USING ER/STUDIO > COMMON TASKS Copy
- Page 71 and 72: USING ER/STUDIO > COMMON TASKS Chan
- Page 73 and 74: USING ER/STUDIO > COMMON TASKS 3 To
- Page 75 and 76: USING ER/STUDIO > COMMON TASKS The
- Page 77 and 78: USING ER/STUDIO > COMMON TASKS 4 Co
- Page 79: USING ER/STUDIO > COMMON TASKS Sync
- Page 83 and 84: USING ER/STUDIO > COMMON TASKS Adva
- Page 85 and 86: USING ER/STUDIO > COMMON TASKS Asso
- Page 87 and 88: USING ER/STUDIO > COMMON TASKS Comp
- Page 89 and 90: USING ER/STUDIO > COMMON TASKS Dime
- Page 91 and 92: USING ER/STUDIO > COMMON TASKS •
- Page 93 and 94: USING ER/STUDIO > COMMON TASKS See
- Page 95 and 96: USING ER/STUDIO > COMMON TASKS The
- Page 97 and 98: USING ER/STUDIO > COMMON TASKS The
- Page 99 and 100: USING ER/STUDIO > COMMON TASKS •
- Page 101 and 102: USING ER/STUDIO > COMMON TASKS 3 In
- Page 103 and 104: USING ER/STUDIO > COMMON TASKS Chan
- Page 105 and 106: USING ER/STUDIO > COMMON TASKS •
- Page 107 and 108: USING ER/STUDIO > COMMON TASKS Shap
- Page 109 and 110: USING ER/STUDIO > COMMON TASKS Addi
- Page 111 and 112: USING ER/STUDIO > DEVELOPING THE LO
- Page 113 and 114: USING ER/STUDIO > DEVELOPING THE LO
- Page 115 and 116: USING ER/STUDIO > DEVELOPING THE LO
- Page 117 and 118: USING ER/STUDIO > DEVELOPING THE LO
- Page 119 and 120: USING ER/STUDIO > DEVELOPING THE LO
- Page 121 and 122: USING ER/STUDIO > DEVELOPING THE LO
- Page 123 and 124: USING ER/STUDIO > DEVELOPING THE LO
- Page 125 and 126: USING ER/STUDIO > DEVELOPING THE LO
- Page 127 and 128: USING ER/STUDIO > DEVELOPING THE LO
- Page 129 and 130: USING ER/STUDIO > DEVELOPING THE LO
USING <strong>ER</strong>/STUDIO > COMMON TASKS<br />
Page 4<br />
For each operation, select the submodels you want to synchronize with the target model. The available<br />
operations (update, delete) depend on the submodel chosen. If this is a frequently updated submodel, you may<br />
want to save all the wizard settings in a Quick Launch file. The file will load your selections when you next use<br />
the utility if you select it upon launching the utility. You can load the quick launch file and make changes to it and<br />
then save the changes if you want.<br />
Notes<br />
• To make changes to both the source and target models, run the utility twice, reversing the source and target the<br />
second time you run the utility.<br />
• The available operations (update, delete) will depend on the submodel chosen and the differences that exist<br />
between the source and target submodels. For example, if the source contains updates not reflected in the<br />
target, then the update operation will be available.<br />
Copying a Database Object to a Submodel (Apply to Submodel)<br />
You can replicate database objects by copying the object and then pasting it to each submodel individually or you can<br />
use the Apply to Submodel function to paste an object into multiple submodels within the same model simultaneously.<br />
1 In either the Data Model Explorer or the Data Model Window, right-click the object you want to copy to one or<br />
more submodels in the active model and then click Apply to Submodel.<br />
2 In the Apply to Submodel dialog, individually select the submodels you want to copy the object to, or select the<br />
model to copy the object to the main model and all submodels of the active model.<br />
NOTE: In the Apply to Submodel dialog, clicking Place New Object Near Existing Objects prevents the<br />
new object from being placed randomly in the Data Model Window. This can be important when<br />
working with large models and submodels.<br />
Establishing Database Security<br />
Define and establish database security to, for example, inform data model reviewers and database administrators of<br />
the security required for data model objects when these objects are implemented on a DBMS.<br />
This section includes the following topics:<br />
• Creating and Editing Database Users<br />
• Creating and Editing Database Roles<br />
• Associating Database Users with New Database Roles<br />
• Associating Database Roles with New Database Users<br />
• Changing Database Roles Associated with Existing Database Users<br />
• Changing Database Users Associated with Existing Database Roles<br />
• Granting and Revoking Permissions to Modify Database Objects<br />
Creating and Editing Database Users<br />
Granting database access, authorities, and privileges to users and groups is one of the most important ways to ensure<br />
data security.<br />
EMBARCAD<strong>ER</strong>O TECHNOLOGIES > <strong>ER</strong>/STUDIO® 8.0.3 US<strong>ER</strong> GUIDE 80