Oracle Query Result Cache Support

DataSunrise 12.1 brings Query Result Cache support to Oracle Database. When an Oracle instance runs in Proxy mode, DataSunrise can cache repeated SELECT query results at the proxy level, helping reduce unnecessary database workload and improve response time for frequently executed read-only queries.

For applications that repeatedly request the same data, Oracle Query Result Cache support gives DataSunrise users a practical way to reduce database round trips while keeping traffic control at the proxy layer.

Why Query Result Cache Matters

Many enterprise applications execute the same read-only queries again and again. Dashboards refresh the same widgets, applications load reference data, reports reuse filters, and users reopen screens that request identical result sets.

Without caching, the proxy forwards each repeated request to Oracle, and the database processes it again. Under high traffic, this can create avoidable load and increase response time for users.

Query Result Cache helps by storing eligible SELECT query results at the DataSunrise proxy level. When an application runs the same cacheable query again and the cached entry remains valid, DataSunrise can return the result directly from cache.

Oracle Support in DataSunrise 12.1

Oracle databases now use the same Result Cache settings and monitoring workflow as other supported database types.

Administrators configure the feature per database instance. For an Oracle instance in Proxy mode, open Result Cache Settings, enable Request Result Cache, and define the cache limits that fit the workload.

Key settings include:

• Cached Lifetime: time-to-live for cached results
• Max Memory: maximum memory allocated for cached result sets
• Max Cache Entries: maximum number of cached results
• Max Cached Result Size: size limit for a single cached result
• Max Cacheable Query Length: query length limit for cacheable requests

DataSunrise isolates cached results per database user, database, and instance, so users do not share cached data.

Monitoring Cache Performance

DataSunrise provides live cache statistics under Monitoring -> Performance -> Result Cache Rate. This makes it easy to confirm whether DataSunrise serves repeated Oracle SELECT queries from cache and whether cache limits need adjustment.

The monitoring view tracks:

• Hit rate
• Hits and misses
• Stored cache entries
• Current cache size
• Evictions
• Invalidations

These statistics help teams tune cache lifetime and memory limits based on real query behavior instead of guesswork.

Cache Behavior and Limitations

Query Result Cache targets repeated read-only SELECT traffic. DataSunrise passes non-cacheable statements through normally and leaves cache statistics unchanged.

DataSunrise does not cache the following query types:

• INSERT, UPDATE, DELETE, stored procedures, and other non-SELECT operations
• Queries with volatile functions such as CURRENT_TIMESTAMP, RANDOM, UUID, or similar values
• Queries that reference system catalogs or temporary tables
• Queries with locking clauses such as FOR UPDATE

Cached results remain valid until their TTL expires, an administrator clears the cache, or memory and entry limits evict the entry. The cache does not automatically invalidate entries when the underlying data changes, so choose TTL values according to application freshness requirements.

Better Performance Options for Oracle Workloads

With Oracle Query Result Cache support, DataSunrise 12.1 helps reduce repetitive Oracle read workload while continuing to provide database security and monitoring capabilities through Proxy mode.

For setup details, see the updated Query Result Cache section in the DataSunrise User Guide.