Tenant Identifier Translation Using Record Headers and Bitmaps
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Translating tenant identifiers in multi-tenant databases is computationally intensive, especially when replacing identifiers for a group of records, such as during cloning for sandboxing.
Innovation Solution
The solution involves removing the tenant identifier from the record columns and storing it in the record header, using a bitmap to track column locations, and updating the key with a new tenant identifier during cloning, ensuring efficient translation by minimizing column-level updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If tenant identifier translation is performed by updating column values in database records, then the tenant identifier can be changed from old to new, but the computational overhead increases significantly
Solution Approach 1:
The patent extracts the tenant identifier value from the database record columns and stores it separately in the record header. This separation allows the identifier to be updated independently without modifying the actual column data, thereby reducing computational overhead while maintaining translation capability
Solution Approach 2:
The patent introduces a bitmap as an intermediary structure to track which columns contain tenant identifier values. This bitmap serves as a mediator between the record header and the actual column data, enabling efficient identification and update of relevant columns without scanning or processing unnecessary data
2Ease of operation
If tenant identifier is stored in record columns, then the identifier is easily accessible, but updating identifiers for multiple records becomes computationally intensive
Solution Approach 1:
The patent segments the tenant identifier storage into two parts: the record header stores the identifier value, while the bitmap segments track which columns reference this identifier. This segmentation allows the identifier to be updated once in the header while automatically affecting all relevant columns, improving bulk update efficiency
Solution Approach 2:
The patent performs preliminary action by pre-storing the tenant identifier value in the record header and pre-computing the bitmap that identifies relevant columns. This preparation work is done once, enabling rapid identification and updating of all columns that need to be translated without repeated analysis
Data Source
AI summary
Systems, devices, and techniques are disclosed for translation of tenant identifiers. A record may be received. A value of a tenant identifier for the record may be determined from a key for the record or a scan descriptor. The value of the tenant identifier in the key for the record may be replaced with a new value for the tenant identifier. A bitmap stored in a record header of the record may be used to identify columns of the record that stored an encoded value of the tenant identifier. An encoded new value of the tenant identifier may be stored in columns identified by the bitmap stored in the record header that include an attribute indicating that tenant identifier translation is enabled.