Unified Query Plan Views for Consistent Database Plan Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database systems face challenges in maintaining consistency and reliability across disparate query plan representations due to fragmented implementations, complicating the extension of functionalities and introduction of new use cases.

Innovation Solution

A unified framework is introduced that treats query plans as views, allowing for a declarative definition of plan views decoupled from underlying implementations, enabling consistent and reliable generation of query plan variants for various use cases.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If disparate implementations are used for each query plan representation, then specific logic can be tailored for each use case, but maintenance challenges and inconsistencies arise

Engineering Contradiction:
Improveuse case specific logicVSAvoidconsistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a universal query plan representation framework that serves multiple use cases through a single standardized interface. The QueryPlanNode class and its standardized fields provide a common foundation that can be used for hashing, signature generation, visual representation, and other purposes, eliminating the need for disparate implementations while maintaining reliability and consistency across all use cases.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If each query plan representation requires specific logic, then functionality can be optimized for each purpose, but the process of ensuring consistency and reliability becomes complicated

Engineering Contradiction:
Improvefunctionality optimizationVSAvoidimplementation complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the query plan representation into distinct, standardized components (QueryPlanNode with specific fields like operator, inputs, outputs, and metadata). This segmentation allows each component to be independently optimized for specific purposes while maintaining overall consistency. The modular structure enables targeted functionality optimization without complicating the overall implementation, as each segment can be processed independently according to its specific requirements.

Inventive Principle:
Principle #1Segmentation

3Ease of manufacture

If fragmented codebases are used for different query plan representations, then each can be developed independently, but extending functionalities or introducing new use cases becomes difficult

Engineering Contradiction:
Improveindependent developmentVSAvoidextensibility
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent merges previously fragmented query plan representation codebases into a unified framework centered around the QueryPlanNode class. This consolidation maintains the ability to develop different representations independently by selecting and processing specific fields, while simultaneously improving extensibility through a common base class that can be extended for new use cases without navigating isolated codebases.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12561325B1Query plan view framework for management of database query plans
Publication Date: 2026.02.24 SNOWFLAKE INC
  • US12561325B1 patent drawing
  • US12561325B1 patent drawing
  • US12561325B1 patent drawing

AI summary

Methods, systems, and computer programs are presented for generating and managing query plan representations using a unified framework based on a common query plan configuration. The system includes a memory with instructions and one or more computer processors. The instructions, when executed, cause the system to provide a user interface (UI) for a development tool to create a configuration for a plan builder. The UI offers options to create a plurality of query plans, including a logical query plan, a physical query plan, a query plan hash, and a query plan signature. The system receives parameters to create the configuration and select a query plan from the plurality of query plans. The system generates a first query plan based on the parameters and causes the presentation of the first query plan on a display.