Database Object Sharing via Provider-Reader Link Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional database systems face inefficiencies due to duplicative storage of static data across multiple database instances, requiring recreation of this data whenever a new environment is added, which is wasteful and inefficient.
Innovation Solution
Implementing a system where a provider database instance shares data objects with reader database instances through direct access, using database links and converter pages to map logical page numbers to physical block addresses, allowing efficient access to shared data without the need for redundant storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If static data is stored in multiple database instances for each vendor environment, then each database can operate independently with complete data, but storage efficiency deteriorates due to duplicative storage
Solution Approach 1:
The patent merges the storage of static data into a single provider database instance that is shared across multiple reader database instances. Instead of each vendor database storing complete copies of static data (product catalogs, customer lists, etc.), the system uses database links to connect reader databases to the provider database, allowing all reader databases to access the same static data through virtual tables. This eliminates redundant storage while maintaining data availability across all vendor environments.
Solution Approach 2:
The patent introduces database links as intermediary structures that connect reader database instances to the provider database instance. These links act as mediators that enable reader databases to access provider database objects without direct physical connections. The database links include mapping information that translates reader database references into provider database locations, facilitating efficient data access while maintaining the independence of individual reader databases.
2Ease of operation
If static data is stored in each databaseinstance, then data can be accessed locally without network dependencies, but the system becomes complex when adding new vendor environments
Solution Approach 1:
The patent implements a universal provider database instance that serves multiple reader database instances simultaneously. The provider database contains a universal set of static data objects that can be accessed by any reader database through database links. This universal structure allows the system to accommodate new vendor environments by simply creating new reader databases that link to the existing provider database, without requiring duplication of static data or complex reconfiguration.
Solution Approach 2:
The patent segments database objects into two categories: static data objects stored in the provider database and dynamic/transactional data stored locally in each reader database. This segmentation allows the system to maintain simple local data for vendor-specific transactions while centralizing static data management. When adding new vendor environments, only the dynamic data needs to be initialized locally, while static data is automatically available through the provider database link.
3Adaptability or versatility
If complete data is recreated for each new vendor environment, then each database has full functionality, but time and resources are wasted on redundant data creation
Solution Approach 1:
The patent performs preliminary action by pre-storing all static data objects in the provider database instance before any reader databases are created. Common static data such as product catalogs, customer master records, and reference tables are prepared once in the provider database and made available to all future reader databases through database links. This eliminates the need to recreate static data for each new vendor environment, significantly reducing setup time and resources.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A system may include reading a provider database mapping of file identifiers to page numbers of the provider database, determining one or more shared database objects of the provider database based on the provider database mapping, and registering the one or more shared.database objects in a local namespace of a reader database.