materialized-views

Precompute complex query results as materialized views for relational databases.

Updated Jun 5, 2026

Search Tags:#query optimization #read models #database performance #data warehousing #materialized views

Ready to run

npx skills add https://github.com/hung-phan/system-skills --skill materialized-views

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: materialized-views
Source: https://github.com/hung-phan/system-skills/tree/main/skills/system-review/references/data-systems/materialized-views
Command: npx skills add https://github.com/hung-phan/system-skills --skill materialized-views

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the performance bottlenecks caused by read-heavy database operations, particularly those involving complex aggregations and joins, by providing precomputed read models that can significantly enhance query performance.

Core Features & Use Cases

Precomputed Aggregations: Store the results of complex queries as materialized views, reducing the need for on-the-fly computation.
Read-Heavy Workloads: Ideal for dashboards, reporting, and other applications where query performance is critical.
Use Case: For instance, in a data warehouse, use this Skill to create a materialized view for a daily sales summary, allowing for quick access to the data without the need for time-consuming aggregations on the fly.

Quick Start

Create a materialized view for the daily sales summary by executing the following SQL command: CREATE MATERIALIZED VIEW daily_sales_summary AS SELECT * FROM sales_data;

Frequently Asked Questions about materialized-views

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I optimize database performance for complex aggregations and joins?▼

Database performance for complex aggregations and joins is optimized by precomputing query results as materialized views. This technique stores read models, reducing on-the-fly computation for high read loads.

What is the best way to handle read-heavy workloads in a data warehouse?▼

The best way to handle read-heavy workloads in a data warehouse is creating materialized views for precomputed aggregations. This allows quick access to data summaries without time-consuming on-the-fly computations.

How do I create a materialized view for a daily sales summary?▼

To create a materialized view for a daily sales summary, execute a SQL command like `CREATE MATERIALIZED VIEW daily_sales_summary AS SELECT * FROM sales_data;` to precompute and store the read model.

When should I use materialized views instead of standard database views?▼

Use materialized views instead of standard views when dealing with read-heavy database operations involving complex aggregations and joins, as they physically store precomputed results rather than executing queries dynamically.

Do I need specific SQL knowledge to implement materialized views?▼

Yes, implementing materialized views requires knowledge of SQL and the specific database system's materialized view features to properly precompute query results and optimize read performance.