Cloned Shared Tables for Multi-Tenant Data Integrity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-tenancy database systems, managing data sharing and separation between shared and tenant-specific containers is challenging, leading to issues like duplicate objects, non-standard behavior upon deletion, and inefficient content management across tenants.
Innovation Solution
The solution involves cloning shared tables in a database system to create updated views in tenant containers, determining object locations using an object catalog, and storing data objects based on their attributes, ensuring objects are stored either in shared or tenant containers to prevent duplicates and maintain standard behavior.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If shared tables are cloned in multi-tenant database systems, then data sharing and separation can be managed, but duplicate objects may be created and system complexity increases
Solution Approach 1:
The patent segments data storage into distinct shared containers and tenant containers, with shared tables cloned to tenant containers only when needed. This segmentation allows independent management of shared and tenant-specific data, preventing duplicates while maintaining data integrity across multi-tenant environments.
Solution Approach 2:
The system performs preliminary actions by cloning shared tables to tenant containers before data storage operations. This pre-cloning ensures that tenant containers have the necessary shared table structures ready, eliminating the need for complex runtime decisions and reducing system complexity during data operations.
2Adaptability or versatility
If data objects are stored in both shared and tenant containers, then data sharing is enabled, but duplicate objects and non-standard behavior occur
Solution Approach 1:
The patent extracts the shared table structure from the shared container and clones it to tenant containers. This extraction allows tenant containers to have their own copy of shared tables, eliminating ambiguity about data location and ensuring consistent behavior across all tenants while maintaining data sharing capability.
Solution Approach 2:
The system creates copies of shared tables in tenant containers rather than maintaining a single shared copy. This copying approach ensures that each tenant has its own data structure, preventing duplicate object issues and ensuring standard behavior while still enabling data sharing through the cloned structures.
3Reliability
If shared tables are cloned to tenant containers, then data separation is improved, but storage space and resource consumption increase
Solution Approach 1:
The patent applies local quality by cloning shared tables only to tenant containers that actually need them, rather than cloning to all containers uniformly. This selective cloning approach optimizes storage space by creating copies only where necessary while maintaining effective data separation where needed.
Data Source
AI summary
Methods, systems, and computer-readable storage media for, in response to initiation of a deployment to a multi-tenant system, cloning a shared table in a shared container of a database system to provide a cloned table, the shared table corresponding to a plurality of table views in respective tenant containers, providing, within each tenant container of the tenant containers, an updated view to the cloned table, for a data object of the deployment, determining a previous location of the data object within the database system from an object catalog, and a new location of the data object within the database system from a deploy file, and storing the data object in one of the shared container, and a tenant container of a respective tenant based on one or both of the previous location, and the new location of the data object.