Results Cache in Oracle

Oracle 11g has a new hint telling data to persist in cache for x number of minutes.


The syntax is:

select /*+ result_cache */ * from test.customer

This could be interesting for tables that do not change much, since any change to the table can invalidate the cache. One simple way would be for a token in the INT file marking if the file changes seldom.


Recommendation:
 Investigate further. This could though have some unforeseen impacts. I am leaning towards recommending that we instead look at tuning servers for more memory (which also caches) and client side cache.

 

Data Security with Flex2SQL and BTR2SQL Connectivity Products

Data Security with Flex2SQL and BTR2SQL Connectivity Products

The most common reason for Enterprises looking to migrate from legacy Btrieve or DataFlex databases is the urgent need to address security and...

Read More
Why Migrate from Btrieve to PostgreSQL and other Relational Databases?

Why Migrate from Btrieve to PostgreSQL and other Relational Databases?

Introduction Many independent software vendors (ISV) and corporate users still rely on applications that use a category of database collective called...

Read More
Four Challenges in Converting COBOL Applications from ISAM Databases to Relational Databases

Four Challenges in Converting COBOL Applications from ISAM Databases to Relational Databases

COBOL applications are the foundation of numerous essential business functions, especially within the banking, insurance, and government sectors....

Read More