In-Memory Database Merging Transactional and Analytical Workloads
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database management systems are either optimized for transactional workloads or analytical workloads but not both, requiring separate databases and significant effort for reporting, which increases operational costs and reduces performance.
Innovation Solution
An in-memory database system that combines transactional and analytical workloads in a single database, using random access memory to store data, defined views, and integrated analytical services, eliminating the need for separate reporting databases and tuning structures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate databases are used for transactional and analytical workloads, then each database can be optimized for its specific workload, but the overall system complexity increases and data transformation effort is required
Solution Approach 1:
The patent merges transactional and analytical workloads into a single in-memory database system. The database stores both operational data and analytical data in the same memory structure, eliminating the need for separate OLTP and OLAP databases. This allows the system to handle both transactional processing and analytical queries without data transformation or replication between separate systems.
Solution Approach 2:
The in-memory database system provides multi-functionality by supporting both transactional operations and analytical queries within the same platform. The database can execute SQL queries for analytical processing while simultaneously handling transactional data operations, making the system universal for different workload types without requiring separate specialized databases.
2Productivity
If separate reporting database is used, then analytical queries can be performed, but significant effort is required for creating and maintaining tuning structures such as aggregates and indexes
Solution Approach 1:
The system performs preliminary actions by pre-calculating and storing aggregates, summaries, and analytical data structures directly in the in-memory database when transactional data is inserted or updated. This eliminates the need for later ETL processes to create aggregates and indexes for analytical queries, as the data is already prepared in an optimized format for both transactional and analytical workloads.
Solution Approach 2:
The patent combines the functions of transactional data storage and analytical data preparation into a single unified database structure. The same memory-resident tables store both operational transactional data and pre-computed analytical aggregates, eliminating the need for separate reporting databases and their associated maintenance routines for creating and optimizing indexes and aggregates.
3Productivity
If data is stored in slower disk drive devices, then storage cost is reduced, but query performance decreases
Solution Approach 1:
The patent changes the storage parameter from disk-based to memory-based storage. By moving the database from traditional disk drive storage to in-memory storage using RAM, the system achieves dramatically faster data access and query performance. The in-memory architecture allows for rapid random access to data without the I/O bottlenecks of disk-based systems, enabling real-time analytical processing and complex queries to execute instantly.
Data Source
AI summary
An in memory database system includes a random access memory to store an in memory database table, a stored set of defined views over the database tables, a stored set of analytical services adapted to provide transaction services and database warehouse services, an engine to run the analytical services on the database table, and an interface to interact with users and provide access to the engine, analytical services, and views to perform transactions and data warehouse functions on the database table.