Database Share Replication Automation via Dependency Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In traditional data platforms, replicating a share of database objects across deployments is a manual and labor-intensive process, requiring users to manually identify and replicate database objects, which is inefficient and prone to errors, especially when accounts are on different deployments.

Innovation Solution

The system automatically analyzes the share definition to determine the necessary database objects for replication, generates a replication group, and configures the replica on the target deployment, allowing for real-time changes and access management without manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual replication of database objects is performed, then users can control the replication process, but the process becomes labor-intensive and error-prone

Engineering Contradiction:
Improvereplication accuracyVSAvoidreplication effort
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs automatic share replication by analyzing share definitions, identifying dependent database objects, and executing replication to target deployments without manual intervention. The database system self-services the replication process, eliminating the need for users to manually identify and replicate each database object while ensuring accuracy through automated dependency analysis.

Inventive Principle:
Principle #25Self-service

2Productivity

If automatic share replication is implemented, then the replication process is streamlined and errors are reduced, but the system complexity increases

Engineering Contradiction:
Improvereplication efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces a share replication mechanism that acts as an intermediary between the source share definition and the target deployment. This intermediary automatically analyzes the share definition, identifies dependent database objects, and coordinates the replication process, thereby streamlining productivity while managing system complexity through a structured intermediate layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary analysis of the share definition before replication, identifying all dependent database objects and their relationships in advance. This preliminary action ensures that the actual replication process is streamlined and efficient, as all necessary objects and dependencies are pre-identified and prepared for replication.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If manual identification of database objects is required, then users can verify each object, but the process becomes time-consuming and labor-intensive

Engineering Contradiction:
Improveobject identification accuracyVSAvoidreplication time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system replaces the manual mechanical process of identifying and verifying database objects with an automated computational analysis mechanism. The system automatically analyzes share definitions, traces dependencies, and identifies all relevant database objects through programmatic processing, thereby achieving precise object identification without the time loss associated with manual verification.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS12135734B2Replication of share across deployments in database system
Publication Date: 2024.11.05 SNOWFLAKE INC
  • US12135734B2 patent drawing
  • US12135734B2 patent drawing
  • US12135734B2 patent drawing

AI summary

Various embodiments provide for replicating a share across deployments of a data platform, where the share can be on a source deployment and the share can be replicated on one or more target deployments, and where the share is replicated with one or more database objects of the source deployment associated with the share. Some embodiments analyze the share to be replicated and, based on the analysis, determine one or more database objects that would be replicated to the one or more target deployments to enable a replica of the share on the one or more target deployments.