Shared Data Set with Delta Table for User-Specific Changes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional database systems require separate databases for each customer, leading to inefficiencies when companies collaborate, as entire data sets need to be copied, and current data marketplaces provide data independently, lacking mechanisms for shared data sets across multiple users.

Innovation Solution

Implementing a system that provides a common shared data set accessible by multiple users, with changes tracked using a delta table to allow user-specific modifications without propagating them to all users, and enabling integration of purchased data sets into a shared database structure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate databases are used for each customer, then data integrity and security are maintained, but data sharing efficiency and resource utilization deteriorate

Engineering Contradiction:
Improvedata integrityVSAvoiddata sharing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments data into shared data sets and user-specific changes stored in separate delta tables. This allows the core shared data to be efficiently shared across multiple users while individual customizations are isolated in separate tables, maintaining data integrity for the shared portion while enabling efficient access and collaboration.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism (delta table) that mediates between the shared database and user-specific modifications. The delta table acts as a buffer that stores changes without directly modifying the shared data, allowing users to have personalized views while the underlying shared data remains intact and efficiently accessible to all users.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If copies of entire data sets are provided for collaboration, then data availability is improved, but resource consumption and storage requirements worsen

Engineering Contradiction:
Improvedata availabilityVSAvoidstorage requirements
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent extracts only the necessary user-specific changes from the shared data set and stores them separately in delta tables. Instead of copying entire data sets for collaboration, the system extracts and stores only the modifications needed for each user, dramatically reducing storage requirements while maintaining data availability through the shared base data set.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses a form of copying where the shared data set is logically copied to multiple users through the shared database, but physical storage is optimized by storing only the differences (delta tables) rather than full copies. This allows efficient data availability without the storage overhead of traditional full copies.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If user-specific changes are propagated to all users, then customization is improved, but data integrity and other users' experience worsen

Engineering Contradiction:
ImprovecustomizationVSAvoiddata integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies local quality by allowing each user to have their own delta table containing user-specific changes, while the shared data set maintains uniform quality and integrity. Each user's customization is localized to their own delta table, preventing any single user's changes from affecting the overall data integrity or other users' experiences with the shared data.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent segments the data structure into shared portions and user-specific portions. The shared data set maintains data integrity and consistency for all users, while user-specific changes are segmented into separate delta tables. This segmentation ensures that customizations remain isolated and cannot compromise the integrity of the shared data or other users' experiences.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10503728B2Shared data set with user-specific changes
Publication Date: 2019.12.10 SALESFORCE INC
  • US10503728B2 patent drawing
  • US10503728B2 patent drawing
  • US10503728B2 patent drawing

AI summary

Methods and systems are described for shared data sets with user-specific changes in an on-line services environment. In one embodiment, a method includes, receiving a request for data stored in a shared database from a user, identifying the requesting user, retrieving the requested data from the shared database, determining whether there are user-specific changes for the retrieved data, changing the retrieved data using the user-specific changes, and supplying the requested data to the user.