Relational Resource Database Indexing for Large Attribute Queries
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current resource management systems are not scalable for new resource types or new resource attributes, and querying resource instances based on attributes that include an array of objects or large size attribute values is inefficient, leading to slow queries or service downtime.
Innovation Solution
A scalable resource management system is designed with modifiable relational tables that store separate object attributes in the attribute table and a separate value index table, excluding large or infrequently queried attribute values, to facilitate efficient querying.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all attribute values are stored in the value index table, then query coverage is complete, but the index table becomes too large and maintenance overhead increases
Solution Approach 1:
The patent segments the value index table into two parts: a main value index table storing only index information (attribute name, instance ID, value ID) and a separate value table storing actual attribute values. This segmentation allows the index table to remain small and efficient while the value table handles large data, resolving the contradiction between complete query coverage and manageable index size.
Solution Approach 2:
The patent extracts large attribute values from the value index table and stores them separately in a dedicated value table. The value index table retains only essential indexing data (value ID, attribute name, instance ID), enabling fast queries without burdening the index structure with large data, thus maintaining both query coverage and index efficiency.
2Loss of information
If the system stores detailed information for all resource attributes, then data completeness is improved, but query performance degrades due to large data size
Solution Approach 1:
The patent segments data storage into two distinct tables: the value index table for fast access to attribute metadata and the value table for storing actual large attribute values. This segmentation enables the system to maintain complete data information while achieving fast query performance through efficient indexing.
Solution Approach 2:
The patent introduces a value ID as an intermediary between the value index table and the value table. This intermediary enables fast queries by resolving attribute lookups through the compact index table while maintaining access to complete detailed information in the value table, thus balancing data completeness and query speed.
3Stability of the object's composition
If the database schema is fixed, then system stability is improved, but adaptability to new resource types and attributes deteriorates
Solution Approach 1:
The patent implements a dynamic database schema where the attribute table can accommodate new resource types and attributes without requiring schema migrations. The separation of index metadata from actual values allows the system to dynamically add new attribute types and resource categories while maintaining system stability through the consistent core table structure.
Solution Approach 2:
The patent creates a universal attribute table structure that can store any resource type and attribute combination through standardized columns (instance ID, attribute name, value ID). This universal design enables the system to adapt to new resource types and attributes while maintaining a stable core database structure, resolving the contradiction between stability and adaptability.
Data Source
AI summary
Systems and methods for resource management using a scalable resource management database are provided. A resource management tool accesses a resource management database. The resource management tool determines a size of an attribute value corresponding to an attribute of a resource instance satisfies a predetermined size threshold. The resource management tool determines a query frequency associated with the attribute value satisfies a predetermined frequency threshold. The resource management tool creates a value index table based on a value table, the value index table excluding the attribute value satisfying the predetermined size threshold and the predetermined frequency threshold.