ER/Studio - Embarcadero Technologies Product Documentation

ER/Studio - Embarcadero Technologies Product Documentation ER/Studio - Embarcadero Technologies Product Documentation

docs.embarcadero.com
from docs.embarcadero.com More from this publisher
24.12.2012 Views

USING ER/STUDIO > DEVELOPING THE PHYSICAL MODEL • Reuse Existing File: If Use Oracle Managed Files to automatically generate Defaults is not enabled, this option is available. If selected, lets you reuse an existing datafile, which the database manager overwrites the first time the file is accessed. Storage page/tab • If the table space of an Oracle table space is dictionary managed, as specified on the Name tab of the editor, then define the parameters of the extents on this tab. • Specify the containers for the tablespace below: Specify an absolute or relative directory name. The relative path is relative to the database directory. If the directory name does not exist, it will be created. NOTE: Click Add only if you want to specify another container. • Select a NodeGroup to assign to the tablespace: Specify either a nodegroup or a database partition number. • Select a page size: The page size must be the same as the page size of the buffer pool that is associated with the database. Options page/tab • Extent Size: Specify the number of pages that will be written to a container before writing to the next container. The database manager cycles through the containers as it stores data. The default extent size is specified by the database configuration parameter DFT_EXTENT_SZ. • Prefetch Size: Specify the number of pages that will be read when prefetching tablespace data. The default prefetch size is specified by the database configuration parameter DFT_PREFETCH_SZ. • Overhead: Specifies the overhead, disk seek, and latency time of the I/O controller. This should be an average for all containers belonging to the tablespace. This value is used during query optimization to determine the I/O cost. • Transfer Rate: Specifies the time required to read one page into memory. This should be an average for all containers belonging to the tablespace. This value is used during query optimization to determine the I/O cost. • Select the recovery status: If ON is selected, dropped tables in this tablespace may be recovered using the ROLLFORWARD command with the RECOVER TABLE ON option. Options 1 page/tab • GBP Cache: Specifies a group buffer pool cache. • Sizing: Specifies the settings for the different Sizing parameters: • If you are creating a non-partitioned tablespace, enter a value between 1 and 255 in the Max rows per page field. • If you are creating a partitioned tablespace, enter the number of partitions you want to create for the tablespace (between 1 and 254) in the Number of Partitions field, then select a size for the partitions from the Partition Size (DSSIZE) list. Enter a value between 1 and 255 in the Max rows per page field. • If you are creating a segmented tablespace, select a value from the Segment Size list, and enter a value between 1 and 255 in the Max rows per page field. • If you are creating an LOB tablespace, select a value from the Partition Size (DSSIZE) list. • TRACKMOD: When set to Yes, the database manager tracks database modifications to enable the backup utility to detect which subsets of the database pages should be examined by an incremental backup and included in the backup image if necessary. Options 2 page/tab • Locking: To control concurrent access and prevent uncontrolled data access, you can create locks which associates a database manager resource with an application, called the lock owner, to control how other applications access the same resource. The Lock Size determines the granularity of the locks. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 208

USING ER/STUDIO > DEVELOPING THE PHYSICAL MODEL • Maximum Locks: Set this to a low number to avoid contention. Setting LOCKMAX to zero increases tablespace availability by preventing lock escalations which can lock the tablespace. Setting LOCKMAX to SYSTEM allows the database manager to control the maximum number of locks by a setting in the database configuration file. • Close Rule: Determines whether the data sets can be closed when the table space is not in use, and the limit on the number of open data sets (DSMAX) is reached. If you select No, no data sets can be closed. However, if DSMAX is reached and no CLOSE YES page sets exist, then even CLOSE NO page sets will be closed. • Partitions: For information on partition parameters, see Partitioning a Table. Definition page/tab Enter or edit a definition for the tablespace. If the target database supports it, ER/Studio adds this definition as a comment when generating SQL code. DDL page/tab Displays the CREATE TABLESPACE statement needed to build the tablespace. ER/Studio uses the platform-specific parser of the model’s selected database platform to generate the tablespace. Attachment Bindings page/ tab Bind an external piece of information, or attachment to the tablespace. You can also remove an attachment from an object, override an attachment binding’s default value, or change the position of a bound attachment. To override the value of the attachment you have moved to the Selected Attachments grid, double-click the Value field of the target attachment. ER/Studio opens the Value Override Editor or a list depending on the attachment datatype. Attachments are created in the Attachments folder of the Data Dictionary. For more information, see Attaching External Documents to the Data Model. Creating and Editing Database Schemas A database schema is a collection of unique objects in a namespace. Schemas allow you to group tables and other related objects together, such as a table and an index. Once the schema has been defined you can The following database platforms support Schemas: • IBM DB2 for LUW 5.x, 6.x, 7.x, 8.x, and 9.x • Microsoft SQL Server 2005 and 2008 NOTE: The Database Schema Wizard and Database Schema Editor share the same options, except for Attachment Bindings options which are present only in the editor. Create a Database Schema 1 In the Data Model Explorer, expand the Physical Main Model, right-click the Schema node and then click New Database Schema. 2 Complete the Database Schema Wizard and then click Finish to create the database schema. TIP: Once you have created the schema, you can edit it by right-clicking the schema you want to change, and then selecting Edit Schema. The following describe options that require additional explanation: Object Privilege page/tab Sets access roles and user permissions for the schema. Keep in mind that the more specific permissions are, the more time you may have to spend maintaining and updating them. The Roles and Users must be previously assigned to appear in the Sequence Editor. For more information, see Granting and Revoking Permissions to Modify Database Objects. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 209

USING <strong>ER</strong>/STUDIO > DEVELOPING THE PHYSICAL MODEL<br />

• Maximum Locks: Set this to a low number to avoid contention. Setting LOCKMAX to zero increases tablespace<br />

availability by preventing lock escalations which can lock the tablespace. Setting LOCKMAX to SYSTEM allows the<br />

database manager to control the maximum number of locks by a setting in the database configuration file.<br />

• Close Rule: Determines whether the data sets can be closed when the table space is not in use, and the limit on<br />

the number of open data sets (DSMAX) is reached. If you select No, no data sets can be closed. However, if<br />

DSMAX is reached and no CLOSE YES page sets exist, then even CLOSE NO page sets will be closed.<br />

• Partitions: For information on partition parameters, see Partitioning a Table.<br />

Definition page/tab<br />

Enter or edit a definition for the tablespace. If the target database supports it, <strong>ER</strong>/<strong>Studio</strong> adds this definition as a<br />

comment when generating SQL code.<br />

DDL page/tab<br />

Displays the CREATE TABLESPACE statement needed to build the tablespace. <strong>ER</strong>/<strong>Studio</strong> uses the<br />

platform-specific parser of the model’s selected database platform to generate the tablespace.<br />

Attachment Bindings page/ tab<br />

Bind an external piece of information, or attachment to the tablespace. You can also remove an attachment from<br />

an object, override an attachment binding’s default value, or change the position of a bound attachment. To<br />

override the value of the attachment you have moved to the Selected Attachments grid, double-click the Value<br />

field of the target attachment. <strong>ER</strong>/<strong>Studio</strong> opens the Value Override Editor or a list depending on the attachment<br />

datatype. Attachments are created in the Attachments folder of the Data Dictionary. For more information, see<br />

Attaching External Documents to the Data Model.<br />

Creating and Editing Database Schemas<br />

A database schema is a collection of unique objects in a namespace. Schemas allow you to group tables and other<br />

related objects together, such as a table and an index. Once the schema has been defined you can<br />

The following database platforms support Schemas:<br />

• IBM DB2 for LUW 5.x, 6.x, 7.x, 8.x, and 9.x<br />

• Microsoft SQL Server 2005 and 2008<br />

NOTE: The Database Schema Wizard and Database Schema Editor share the same options, except for<br />

Attachment Bindings options which are present only in the editor.<br />

Create a Database Schema<br />

1 In the Data Model Explorer, expand the Physical Main Model, right-click the Schema node and then click New<br />

Database Schema.<br />

2 Complete the Database Schema Wizard and then click Finish to create the database schema.<br />

TIP: Once you have created the schema, you can edit it by right-clicking the schema you want to<br />

change, and then selecting Edit Schema.<br />

The following describe options that require additional explanation:<br />

Object Privilege page/tab<br />

Sets access roles and user permissions for the schema. Keep in mind that the more specific permissions are,<br />

the more time you may have to spend maintaining and updating them. The Roles and Users must be previously<br />

assigned to appear in the Sequence Editor. For more information, see Granting and Revoking Permissions to<br />

Modify Database Objects.<br />

EMBARCAD<strong>ER</strong>O TECHNOLOGIES > <strong>ER</strong>/STUDIO® 8.0.3 US<strong>ER</strong> GUIDE 209

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!