24.12.2012 Views

ER/Studio - Embarcadero Technologies Product Documentation

ER/Studio - Embarcadero Technologies Product Documentation

ER/Studio - Embarcadero Technologies Product Documentation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

Definition page/tab<br />

Enter or edit a definition or description for the materialized view. If the target database supports it, <strong>ER</strong>/<strong>Studio</strong><br />

adds this definition as a comment when generating SQL code.<br />

DDL page/tab<br />

Displays the CREATE SUMMARY TABLE AS ... (SELECT ...) statement needed to build the node group.<br />

<strong>ER</strong>/<strong>Studio</strong> uses the platform-specific parser of the model’s selected database platform to generate the<br />

materialized query table.<br />

Attachment Bindings tab<br />

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

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

attachment. To override the value of the attachment you have moved to the Selected Attachments grid,<br />

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

depending on the attachment datatype. Attachments are created in the Attachments folder of the Data Dictionary.<br />

For more information, see Attaching External Documents to the Data Model.<br />

Notes<br />

• The materialized query table is not populated when first created. You must explicitly populate the materialized<br />

query table using the REFRESH TABLE statement for system-maintained materialized query tables or by using<br />

the LOAD utility, INS<strong>ER</strong>T statement or the REFRESH TABLE statement for user-maintained materialized query<br />

tables.<br />

Creating and Editing Materialized Views<br />

The performance of data warehousing and decision support system tools can be significantly increased when<br />

materialized views are used. Materialized views increase the speed of queries that access many records, allowing you<br />

to query terabytes of data in seconds. A materialized view is a pre-computed table comprising aggregated or joined<br />

data from fact and possibly dimension tables which is also known as a summary or aggregate table. An example of<br />

such a pre-defined query would be the sum of sales by region for a specific period of time. The storage requirements<br />

of the pre-computed summarizations and data joins of a materialized view are small compared to the original source<br />

data. A materialized view creates a real table that can be indexed and analyzed.<br />

The following database platforms support materialized views:<br />

• Oracle 8.x, 9i, 10g, and 11g<br />

NOTE: The Oracle Materialized View Wizard and Oracle Materialized View Editor share the same<br />

options, except for PreSQL & PostSQL, Permissions, and Attachment Bindings options which are<br />

available only in the editor.<br />

Create a Materialized View<br />

1 In the Data Model Explorer, expand the Physical Main Model, right-click the Materialized Views node, and<br />

then click New Materialized View.<br />

2 Complete the Oracle Materialized View Wizard and then click Finish to create the materialized view.<br />

TIP: Once you have created the materialized view, you can edit it by right-clicking the materialized view<br />

you want to change, and then clicking Edit Materialized View.<br />

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

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

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

Saved successfully!

Ooh no, something went wrong!