In a database supporting an OLTP workload, tables are frequently updated on both key and non- keycolumns. Reports are also generated by joining multiple tables. Which table organization or type…

The correct answer is A. heap table with a primary key index. Do not cluster tables if the application joins them only occasionally or modifies their common column values frequently. Modifying a row's cluster key value takes longer than modifying the value in an unclustered table, because Oracle might need to migrate the modified row to…

New Features for Performance

Question

In a database supporting an OLTP workload, tables are frequently updated on both key and non- keycolumns. Reports are also generated by joining multiple tables. Which table organization or type would provide the best performance for this hybrid workload?

Options

Aheap table with a primary key index
Bexternal table
Chash clustered table
Dglobal temporary table
Eindex clustered table

How the community answered

(35 responses)

A
86% (30)
B
3% (1)
D
3% (1)
E
9% (3)

Explanation

Do not cluster tables if the application joins them only occasionally or modifies their common column values frequently. Modifying a row's cluster key value takes longer than modifying the value in an unclustered table, because Oracle might need to migrate the modified row to another block to maintain the cluster.

Topics

#heap table#table organization#OLTP performance#hybrid workload

Community Discussion

No community discussion yet for this question.

Full 1Z0-067 Practice