User-Filtered Snapshot Generation for Cloud Database Tables

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Generating backups for large cloud databases and tables is resource-intensive and inefficient, as it requires copying extensive data, consuming significant storage and processing resources.

Innovation Solution

Creating a snapshot of user data by filtering and mapping data structures to specific data pages, rather than duplicating the entire dataset, and using tags to manage updates efficiently, allowing for nearly instantaneous snapshot creation and minimal resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional backup methods are used to create copies of entire data tables, then data redundancy and reliability are improved, but storage resource consumption and processing time increase significantly

Engineering Contradiction:
Improvedata backup reliabilityVSAvoidstorage resource consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the necessary mapping information from the original data structure rather than copying entire data tables. The snapshot data structure contains references to original data pages instead of duplicating all data, significantly reducing storage consumption while maintaining backup reliability

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates a simplified copy (snapshot) that references the original data rather than a complete duplicate. The snapshot data structure stores mapping relationships that point to the original data pages, providing an efficient backup mechanism that consumes minimal storage resources

Inventive Principle:
Principle #26Copying

2Reliability

If complete data tables are copied for backups, then data redundancy is improved, but processing time and computational resources increase

Engineering Contradiction:
Improvedata backup reliabilityVSAvoidbackup processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the essential mapping relationships needed for backup purposes, creating a lightweight snapshot data structure that can be generated quickly without processing or copying the entire data table, thus reducing backup processing time while maintaining reliability

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent changes the parameter of the backup structure from storing complete data to storing mapping references. This parameter change transforms the backup from a data-intensive operation to a metadata-intensive operation, significantly reducing processing time and computational resource requirements

Inventive Principle:
Principle #35Parameter changes

3Reliability

If traditional snapshot methods are used, then data redundancy is improved, but storage efficiency deteriorates

Engineering Contradiction:
Improvedata snapshot reliabilityVSAvoidstorage efficiency
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent creates an efficient snapshot by copying only the mapping structure rather than the entire data set. The snapshot data structure contains references to original data pages, providing data redundancy for reliability while maintaining high storage efficiency through minimal resource usage

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11010401B2Efficient snapshot generation of data tables
Publication Date: 2021.05.18 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11010401B2 patent drawing
  • US11010401B2 patent drawing
  • US11010401B2 patent drawing

AI summary

A snapshot of data from a table associated with a particular user may be generated. Tree data structures that are distributed across multiple computer systems may be accessed. Each of the tree structures may include data associated with one or more users. At least one tree data structure of the tree data structures that includes data associated with the particular user of the one or more users may be identified. The at least one tree data structure may then be filtered. Filtering may comprise identifying only data that is associated with the particular user. A snapshot of the data associated with the particular user may be generated. Generating the snapshot of the data associated with the particular user comprises generating a data structure that is configured to map to each data page of the at least one tree data structure that includes data associated with the particular user.