Database Trigger Monitoring for Server Change Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database monitoring systems are passive, resource-intensive, and limited in their ability to detect comprehensive changes, often interfering with the database and slowing data processing, while also being simplistic in their monitoring capabilities.
Innovation Solution
A method and system that duplicate data from a server system to a separate hardware system for processing, allowing for comprehensive and continuous monitoring without disturbing the server, enabling more detailed and frequent analysis of changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If monitoring software is loaded on the database server to monitor the database system, then monitoring capability is provided, but the server resources are consumed and data processing is slowed
Solution Approach 1:
The monitoring function is extracted from the database server by placing a database trigger on the server that detects changes and sends notifications to an external monitoring system. This separates the monitoring workload from the database server, allowing the server to focus on data processing while the external system handles monitoring tasks.
Solution Approach 2:
An intermediary component (database trigger) is introduced between the database server and the monitoring system. The trigger acts as a mediator that captures change events and transmits them to the external monitoring system, eliminating the need for resource-intensive monitoring software running directly on the server.
2Reliability
If monitoring software actively monitors the database system, then comprehensive monitoring is achieved, but the server resources are consumed
Solution Approach 1:
Change detection is performed preliminarily by the database trigger at the moment data changes occur, rather than through continuous active monitoring. This event-driven approach ensures comprehensive monitoring of all changes while consuming minimal server resources, as the trigger only activates when necessary.
3Ease of operation
If monitoring systems interfere with database data to carry out monitoring actions, then monitoring actions can be executed, but data processing is potentially slowed
Solution Approach 1:
Monitoring actions are extracted from the database server environment and executed externally. The database trigger sends notifications to an external monitoring system that performs all monitoring actions remotely, eliminating interference with database data and maintaining optimal data processing speed.
4Productivity
If passive monitoring systems are used that are only active when a problem occurs, then resource consumption is reduced, but monitoring capability is limited
Solution Approach 1:
The system performs preliminary change detection using database triggers that are always active at the data level. When changes occur, the trigger immediately detects them and sends notifications to the external monitoring system, which then performs comprehensive analysis. This hybrid approach maintains high resource efficiency while ensuring comprehensive monitoring capability.
Solution Approach 2:
The database trigger provides immediate feedback about data changes to the external monitoring system. This feedback mechanism ensures that the monitoring system is notified of all changes in real-time, maintaining comprehensive monitoring capability while keeping resource consumption low since the heavy lifting is done externally.
Data Source
AI summary
A method and systems for monitoring changes for a server system are disclosed. The server system is operated on a first hardware system. Data is duplicated from the server system, and the data duplicated from the server system is transferred from the first hardware system on which the server system is operated, to a second hardware system separate from the first hardware system. The duplicated data is then processed on the second hardware system to determine a change for the server system. Present duplicated data transferred to the second hardware system may be compared to hosted data on the second hardware system, such as data previously duplicated from the server system. The server system may be a database server system.