Multi-tenant Database Tab Sharing Model
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-tenant database systems, adding custom objects and applications is challenging due to the overwhelming burden on the data dictionary catalog and the lack of support for online DDL in highly concurrent transactional systems, leading to unacceptable delays and maintenance issues.
Innovation Solution
A novel sharing model that allows users to create and customize tabs and tab sets, defining relationships between custom and standard objects and fields, enabling easy sharing and access control, thereby facilitating the management of custom and standard database objects and applications in a multi-tenant environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional DDL is used to create custom objects in multi-tenant database systems, then custom objects can be added to the database schema, but the data dictionary catalog becomes overwhelmed and maintenance becomes nearly impossible
Solution Approach 1:
The patent segments the database schema into a fixed physical schema and variable logical schema. The fixed physical schema maintains a consistent data dictionary catalog structure, while the variable logical schema allows custom objects to be defined through metadata associations without modifying the physical structure. This segmentation resolves the contradiction by enabling custom object creation while preventing catalog overwhelm.
Solution Approach 2:
The patent introduces an intermediary layer between the physical database schema and the logical custom objects. This intermediary uses metadata to map custom objects to existing physical tables and columns, allowing custom objects to be created without direct DDL operations on the physical schema. The intermediary layer absorbs the complexity of custom object variations while maintaining a stable physical catalog.
2Adaptability or versatility
If schema creation is allowed for one organization in a multi-tenant system, then custom objects can be created, but application locks are caused for all other customers
Solution Approach 1:
The patent segments schema creation into logical schema definition (which can be done concurrently) and physical schema mapping (which maintains fixed structure). Multiple organizations can define their custom objects simultaneously without locking, as the system uses metadata associations rather than physical schema modifications. This resolves the reliability issue by eliminating transactional locks during schema creation.
Solution Approach 2:
The patent performs preliminary action by pre-defining the fixed physical schema structure before any custom objects are created. All custom objects are then mapped to this pre-established physical structure through metadata, eliminating the need for concurrent physical schema changes. This preliminary structuring prevents application lockouts while allowing flexible custom object creation.
3Adaptability or versatility
If physical database schema is modified for each tenant, then custom objects can be created, but maintenance burden on DBAs becomes nearly impossible
Solution Approach 1:
The patent segments maintenance responsibilities by separating fixed physical schema maintenance (handled by the system) from variable logical schema customization (handled by tenants through metadata). DBAs no longer need to maintain individual tenant schemas, as the fixed physical structure remains constant while custom objects are defined through non-intrusive metadata associations.
Solution Approach 2:
The patent uses copying by creating logical copies of existing physical tables and columns through metadata associations. Instead of physically creating new tables for each custom object, the system creates virtual copies that map to existing physical structures. This copying approach eliminates the need for DBAs to manage numerous physical schema changes while enabling extensive custom object creation.
4Ease of operation
If tabs and tab sets are created to provide user access to multiple objects, then user interface convenience is improved, but system complexity increases
Solution Approach 1:
The patent implements universality by creating a standardized tab and tab set framework that can access any database object through unified metadata associations. The same tab infrastructure serves multiple purposes: accessing standard objects, custom objects, and defining relationships between objects. This multi-functionality improves user access convenience while managing complexity through a single universal mechanism.
Solution Approach 2:
The patent introduces tabs and tab sets as intermediary layers between users and the complex database object relationships. These intermediaries provide a simplified, standardized interface that abstracts the underlying complexity of multi-object access. Users interact with a consistent tab-based UI while the intermediary layer handles the complex metadata associations and object relationships in the background.
Data Source
AI summary
A sharing model enables users to easily and conveniently create and share standard and custom database objects, and applications, among users or groups of users. The sharing model includes systems and methods that allow users to conveniently create and customize tabs and tab sets that define relationships between custom objects and fields, standard objects and fields, and applications. A tab visually represents a user interface into an element of an application or into a database object. Selection of a tab provides a user access to the object or element of the application represented by the tab. A tab set is a group of related tabs that work as a unit to provide application functionality. New tabs and tab sets may be defined and tab set views may be customized so that an end user can easily and conveniently switch between the various objects and application elements represented by the displayed tabs and tab set views.