Database Statement Tagging for Persistent Control Information
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mechanisms for conveying control information, such as optimizer hints, are limited to query optimizers and do not persist beyond a database session, preventing the transmission of information to background processes or other components outside the session window.
Innovation Solution
Appending a tag to database statements with control information, such as security or priority details, allows this information to be stored and executed by a background server, enabling persistence and communication with other database components even after the user session has ended.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If optimizer hints are used to convey control information, then the query optimizer can determine execution plans more effectively, but the control information cannot be transmitted to background processes or other components outside the session window
Solution Approach 1:
The patent extends the functionality of control information transmission from仅限于 query optimizers to multiple database components including background processes, schedulers, and access control components. The database statement is enhanced to carry control information that can be universally interpreted by different database server components, transforming a specialized mechanism into a multi-functional communication channel.
Solution Approach 2:
The patent introduces an intermediary mechanism where control information is embedded within the database statement itself, acting as a carrier that transports information from the client to various database server components. This intermediary structure allows control information to persist with the database statement throughout its processing lifecycle, enabling reliable transmission beyond the session window to background processes and other components.
2Ease of operation
If control information is stored in session space, then it is readily accessible during the session window, but it becomes unavailable after the session ends
Solution Approach 1:
The patent applies preliminary action by embedding control information directly into the database statement before submission to the database server. This pre-packaging ensures that control information is attached to the statement itself rather than relying on temporary session storage, allowing the information to persist and be accessed by background processes and other components after the session window closes.
3Adaptability or versatility
If optimizer hints are used, then execution plan generation is improved, but other types of control information such as security, priority, and scheduling information cannot be conveyed
Solution Approach 1:
The patent creates a universal control information mechanism that can convey multiple types of control information including security access control, priority scheduling, and resource allocation within a single integrated framework. This eliminates the need for separate mechanisms for different control information types, reducing overall system complexity while expanding functionality.
Solution Approach 2:
The patent segments control information into distinct categories (security, priority, scheduling, etc.) within the enhanced database statement structure. This segmentation allows different components of the database server to selectively process relevant control information while maintaining a unified transmission mechanism, balancing versatility with manageable complexity.
Data Source
AI summary
Sending control information that is associated with a statement that controls how the statement is processed is disclosed. The information is available to the server even after the window session is closed. The information may be contained in a tag appended to the statement. In an embodiment, the information may be viewed by an administrator. The information may determine aspects of how the statement is executed that is not controlled by the execution engine. For example, the information may relate to security access, priority, quality of service, scheduling, and or use supplied routines.