Record Type Bit for Tenant Identifier Translation Indexing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Identifying records that require tenant identifier translation in a multi-tenant database can be computationally intensive, especially when records need to be cloned for sandboxing, as existing methods lack efficiency in pinpointing and updating records with encoded tenant identifiers across multiple columns.
Innovation Solution
Implementing a record type bit in the record header to indicate the presence of encoded tenant identifiers in columns other than the tenant identifier column, allowing for the creation of a partial index to selectively perform tenant identifier translation, reducing computational costs by avoiding full index updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If existing methods are used to identify records requiring tenant identifier translation, then all records must be scanned and checked, but this approach is computationally intensive and inefficient
Solution Approach 1:
The patent applies preliminary action by setting a record type bit in the record header during the cloning process itself, before any translation operation is needed. This bit is set based on whether the record contains encoded tenant identifiers in non-tenant identifier columns. When translation is needed later, the system only needs to check this pre-set bit rather than scanning entire records, dramatically reducing computational resources required at translation time.
Solution Approach 2:
The patent segments the identification process by creating a partial index that only includes records with the record type bit set to indicate they contain encoded tenant identifiers. This segmentation allows the system to work with a subset of records rather than all records, improving productivity while reducing computational energy by focusing only on relevant records.
2Measurement precision
If a full index is created to identify all records with encoded tenant identifiers, then all records can be identified, but this increases device complexity and maintenance overhead
Solution Approach 1:
The patent applies partial action by creating a partial index that only includes records where the record type bit is set to indicate the presence of encoded tenant identifiers. This partial index provides sufficient measurement precision to identify all records needing translation without the complexity of a full index covering all records. The partial index reduces device complexity while maintaining the ability to accurately identify records requiring translation.
3Reliability
If tenant identifier translation is performed on all records, then no records are missed, but computational resources are wasted on records that don't contain encoded identifiers
Solution Approach 1:
The system performs preliminary action by setting the record type bit during record creation or cloning, before translation is needed. This preliminary marking allows the translation process to reliably identify only records that actually contain encoded tenant identifiers, ensuring completeness of translation while avoiding waste of computational resources on records that don't need translation.
Solution Approach 2:
The patent implements feedback through the record type bit that provides information about whether a record contains encoded tenant identifiers. This feedback mechanism allows the translation process to make informed decisions about which records to process, ensuring reliable identification of records needing translation while minimizing unnecessary computational expenditure.
Data Source
AI summary
Systems, devices, and techniques are disclosed for identification of records for post-cloning tenant identifier translation. Records may be received from a database system executing a database executor at a computing device executing a database application. The database application may identify, from among the records, records that include a record header that includes a bit indicating that an encoded value of a tenant identifier is stored in the record in a column of the record that is not a tenant identifier column. The database application may generate an index based on the records identified by the database application. The database application may access the records using the index and replace the encoded value of the tenant identifier stored in columns of the records with an encoded new value of a tenant identifier.