oracle 11g에서 제공하는 result cache 기능에 대한 설명입니다.
shared pool내에 결과가 저장되는 영역이 새로 할당되는 군요.
세션 레벨에서 hint를 통해 지정할 수 있답니다..
Implementing SQL Query Result Cache
The new SQL Query Result Cache enables explicit caching of queries and query fragments in an area of the shared pool called Result Cache Memory.
When a query is executed the result cache is built up and the result is returned.
The database can then use the cached results for subsequent query executions, resulting in faster response times.
Cached query results become invalid when data in the database object(s) being accessed by the query is (are) modified.
You can enable Query Result Cache at the database level using the RESULT_CACHE_MODE initialization parameter in the database initialization parameter file.
The same parameter can also be used at the session level using the ALTER SESSION command.
RESULT_CACHE_MODE can be set to:
* MANUAL : (default) you have to add the RESULT_CACHE hint to your queries in order for results to be cached or to be served out of the cache.
The RESULT_CACHE hint can also be added in sub queries and in-line views.
* FORCE : results are always stored in the Result Cache Memory if possible.
The new SQL Query Result Cache enables explicit caching of queries and query fragments in an area of the shared pool called Result Cache Memory.
When a query is executed the result cache is built up and the result is returned.
The database can then use the cached results for subsequent query executions, resulting in faster response times.
Cached query results become invalid when data in the database object(s) being accessed by the query is (are) modified.
You can enable Query Result Cache at the database level using the RESULT_CACHE_MODE initialization parameter in the database initialization parameter file.
The same parameter can also be used at the session level using the ALTER SESSION command.
RESULT_CACHE_MODE can be set to:
* MANUAL : (default) you have to add the RESULT_CACHE hint to your queries in order for results to be cached or to be served out of the cache.
The RESULT_CACHE hint can also be added in sub queries and in-line views.
* FORCE : results are always stored in the Result Cache Memory if possible.
자세한 내용과 example은 OTN에서..
Improving Application Performance Using Result Cache
'Oracle Database' 카테고리의 다른 글
| Oracle SQLPLUS에서 CASE문 사용하기 (4) | 2009.10.12 |
|---|---|
| oracle 접속 잘 안될때 system state dump 뜨기 (2) | 2009.10.12 |
| Oracle 10g: BIGFILE Type Tablespaces Versus SMALLFILE Type (2) | 2009.10.07 |
| Oracle EXISTS Versus IN (1) | 2009.10.06 |
| Oracle sqlplus에서 변수 사용하기. (1) | 2009.10.06 |