Vertica Query Result Cache Support in DataSunrise 12.2 Release

DataSunrise 12.2 brings Query Result Cache support to Vertica databases. For eligible Vertica proxy traffic, DataSunrise can cache repeated SELECT query results and return cached results for repeated read requests.

This can help reduce repeated database load and improve response time for workloads that often run the same read-only queries.

Why Result Cache Matters for Vertica

Analytical systems often serve dashboards, reports, and recurring queries. Many of those requests repeat the same SELECT statements or request the same result sets with the same filters.

When every repeated request goes back to the database, the system spends resources processing work it may have already completed. Query Result Cache helps by storing eligible query results at the DataSunrise proxy level.

If the same cacheable request appears again while the cached entry remains valid, DataSunrise can return the result from cache instead of forwarding the query to Vertica again.

Vertica Support in DataSunrise 12.2

With this release, Vertica joins the list of database types that can use DataSunrise Query Result Cache. The feature works with Vertica proxy traffic and targets repeated SELECT query results.

The new support is designed to use the existing Result Cache configuration and monitoring workflow. Administrators do not need to learn a separate process for Vertica caching. They can use the same DataSunrise controls to configure cache behavior and watch cache activity.

What Teams Can Gain

Vertica Query Result Cache can be useful when applications or users run repeated read requests through the DataSunrise proxy.

Common cases include:

• Dashboards that refresh the same widgets.
• Reports that reuse the same filters.
• Applications that repeatedly load reference data.
• Users who reopen screens backed by repeated SELECT queries.

For these workloads, cache hits can reduce unnecessary round trips to the database. They can also help make repeated requests respond faster when the cached result is available.

Existing Monitoring Workflow

DataSunrise 12.2 uses the existing Result Cache monitoring workflow for Vertica. Teams can track cache behavior from the same place they use for other supported databases.

This helps administrators confirm whether repeated Vertica SELECT queries are being served from cache and whether cache settings match the workload. If cache activity is low, teams can adjust configuration or review which queries are eligible for caching.

A Practical Performance Option for Vertica

Vertica Query Result Cache support gives DataSunrise users another way to reduce repeated read workload at the proxy layer. It keeps cache configuration and monitoring inside DataSunrise while extending the same workflow to Vertica environments.

See the updated DataSunrise documentation for current Result Cache configuration details and supported Vertica behavior.