Question

An Eventhouse in your Real-Time Intelligence solution stores 18 months of telemetry data for compliance, but analysts only run interactive dashboards against the most recent 30 days. Queries against recent data have become noticeably slower over time, and capacity monitoring shows high memory pressure on the Eventhouse. You need to improve interactive query performance for recent data while retaining all 18 months for occasional audits, keeping costs reasonable. What should you configure?

Accepted Answer

Set the hot cache (caching policy) to 30 days while keeping the retention policy at 18 months on the KQL database or table.

Answer

Reduce the retention policy to 30 days and export older data to a lakehouse via a scheduled pipeline.

Answer

Set both the hot cache policy and the retention policy to 18 months so all data is available for fast queries.

Answer

Create a materialized view that filters the last 30 days and query the view instead of the base table.