Database Tag Propagation Through SQL Object Dependencies

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manual tag propagation in databases is inefficient, fails to scale, and is prone to user errors, leading to unprotected and undiscoverable data due to the manual effort required to keep tags updated across different objects.

Innovation Solution

Implementing automatic tag propagation mechanisms that allow tags and tag-based policies to automatically propagate whenever data is copied or projected, ensuring continuous updating and adherence to object dependencies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual tag propagation is used, then tags can be updated across database objects, but the process is inefficient, fails to scale, and is prone to user errors

Engineering Contradiction:
Improvetag accuracyVSAvoidtag propagation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs automatic tag propagation without requiring manual user intervention. The database automatically identifies dependent objects and propagates tags when source objects are modified, eliminating the need for users to manually update tags across multiple objects while maintaining high accuracy and scalability

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system establishes a feedback mechanism where modifications to source database objects automatically trigger tag propagation to dependent objects. The system monitors changes in source objects and automatically updates tags in dependent objects, ensuring continuous synchronization without manual intervention

Inventive Principle:
Principle #23Feedback

2Reliability

If manual tag propagation is used, then tags can be applied to database objects, but significant manual effort is required to keep tags updated

Engineering Contradiction:
Improvetag consistencyVSAvoidmanual update time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system pre-establishes dependency relationships between database objects before modifications occur. When source objects are modified, the system automatically identifies all dependent objects and propagates tags to them, eliminating the need for manual identification and updating of dependent objects

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The database system automatically maintains tag consistency by detecting modifications to source objects and propagating tags to dependent objects without requiring manual user intervention, thereby maintaining consistency while eliminating manual update time

Inventive Principle:
Principle #25Self-service

3Productivity

If automatic tag propagation is implemented, then tag updates are automated and scalable, but system complexity increases

Engineering Contradiction:
Improvetag propagation efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements automatic tag propagation by establishing a feedback mechanism that monitors modifications to source database objects and automatically triggers tag updates in dependent objects. This automation improves productivity while managing complexity through structured event-driven architecture

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system segments the tag propagation process into distinct components: dependency relationship establishment, modification detection, and tag propagation execution. This segmentation manages system complexity by breaking down the automated process into manageable, independent modules that can be maintained and scaled separately

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20250371036A1Automatic tag propagation
Publication Date: 2025.12.04 SNOWFLAKE INC
  • US20250371036A1 patent drawing
  • US20250371036A1 patent drawing
  • US20250371036A1 patent drawing

AI summary

A tag propagator may obtain a SQL statement. As a result of obtaining the SQL statement, object dependencies between objects referenced in the SQL statement may be determined. Tags associated with the determined object dependencies may be further determined. The tags may be propagated.