Database Pseudo-Tables Reduce Storage Overhead
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Relational databases occupy significant space and consume resources due to the presence of numerous empty tables, which are created and maintained even when no data is stored, leading to inefficient use of storage and processor resources.
Innovation Solution
Implementing pseudo-tables as database views that occupy less space and resources, which are used in place of empty tables, with metadata stored to describe table characteristics, allowing for transparent management through middleware.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If empty tables are created and maintained in the database, then data structure definitions and metadata are available for applications, but storage space is significantly consumed
Solution Approach 1:
The patent creates a copy of the table definition metadata and stores it in the system catalog instead of maintaining the actual empty table structure. This allows the metadata to be available for applications while avoiding the storage consumption of actual empty tables.
Solution Approach 2:
The patent extracts only the essential metadata (table definition, structure information) from the empty tables and stores it in the system catalog. The actual empty table structures are removed, keeping only the necessary descriptive information.
2Adaptability or versatility
If a large number of empty tables are maintained for multiple applications, then each application has its required tables available, but processor resources are consumed for checking and updating data structures
Solution Approach 1:
The patent creates a single system catalog that serves all applications, storing table metadata that can be shared across multiple applications. This eliminates the need for each application to have separate empty tables, reducing processor overhead while maintaining support for multiple applications.
Solution Approach 2:
The patent merges the metadata management of multiple applications into a single system catalog structure. Instead of maintaining separate table definitions for each application, the system consolidates these definitions centrally, reducing the overall number of data structures that need to be checked and updated.
3Ease of operation
If empty tables with basic data structure data are created, then table metadata is available for queries and accesses, but extensive physical space is occupied on persistent storage
Solution Approach 1:
The patent copies table metadata definitions into the system catalog, making them accessible for queries and operations without maintaining actual empty table structures on persistent storage. This provides query accessibility while minimizing storage space usage.
Solution Approach 2:
The patent replaces permanent empty table structures with lightweight metadata entries in the system catalog. These metadata entries serve the same functional purpose but occupy minimal storage space, effectively using a cheaper alternative to the original structure.
Data Source
AI summary
Methods and a system for managing database usage. The methods and system include receiving a request to create a table, determining the table is an empty table, and storing a pseudo-table in a data store in response to determining the table is empty. The pseudo-table may be a database view. Metadata related to a table may be stored in the pseudo-table to describe characteristics of the table. The pseudo-table occupies less space than a corresponding empty table. The system may implement the methods in middleware transparent to the applications.