You are looking for some general design principles that could be used in designing every large scale data warehouse you create. Identify the principle that would have the widest applicability.

Question

Options

• APartition your tables appropriately to produce partition-wise joins.
• BAlways use a star schema or snowflake schema design.
• CDo as much analytics as possible in your BI tools.
• DAlways use Oracle OLAP.

• A
  77% (37)
• B
  4% (2)
• C
  13% (6)
• D
  6% (3)

Explanation

Partition-wise joins can be full or partial. Oracle decides which type of join to use. A full partition-wise join divides a large join into smaller joins between a pair of partitions from the two joined tables. To use this feature, you must equipartition both tables on their join keys, or use Oracle Database can perform partial partition-wise joins only in parallel. Unlike full partition- wise joins, partial partition-wise joins require you to partition only one table on the join key, not both tables. Note: Partition-wise joins reduce query response time by minimizing the amount of data exchanged among parallel execution servers when joins execute in parallel. This significantly reduces response time and improves the use of both CPU and memory In Oracle Real Application Clusters (RAC) environments, partition-wise joins also avoid or at least limit the data traffic over the interconnect, which is the key to achieving good scalability for massive join operations.

No community discussion yet for this question.