You think that result set caching might provide some benefits for your current data warehouse scenario. You perform some analysis on the composition of the queries used in the scenario. Identify the…

Question

Options

• AThe scenario consists mainly of queries that are used infrequently.
• BThe scenario consists mainly of queries that work on data which changes frequently.
• CThe scenario consists mainly of queries with long run times and small result sets.
• DAll data warehouse scenarios will benefit from result set caching.

• A
  10% (3)
• B
  3% (1)
• C
  83% (25)
• D
  3% (1)

Explanation

As its name suggests, the query result cache is used to store the results of SQL queries for re- use in subsequent executions. By caching the results of queries, Oracle can avoid having to repeat the potentially time-consuming and intensive operations that generated the resultset in the first place (for example, sorting/aggregation, physical I/O, joins etc). The cache results themselves are available across the instance (i.e. for use by sessions other than the one that first executed the query) and are maintained by Oracle in a dedicated area of memory. Unlike our homegrown solutions using associative arrays or global temporary tables, the query result cache is completely transparent to our applications. It is also maintained for consistency automatically, unlike our own caching programs.

No community discussion yet for this question.