framework

Job details

Parameters

Job Summary

• Purpose: The primary function of this dbWatch Control Center job is internal maintenance, specifically for the patching or upgrading of the dbWatch engine framework.
• Why: Maintaining and upgrading the dbWatch engine framework is crucial to ensure that the database management functionalities continue to operate efficiently and effectively. This job systematically applies necessary updates or patches, thereby avoiding manual errors and reducing system downtime.
• Manual checking: While not described in the given text, the status of dbWatch engine tasks including those related to maintenance can normally be viewed manually in the database. To achieve this, an example query might be:

SELECT * FROM dbw_tasks WHERE name = 'framework';

Details of the Job’s Operations

• This internal job is specifically designed and named “framework” within the dbWatch engine setup.
• It operates on a pre-set schedule, specifically at 05:40 on the first of every month, to carry out its functions routinely without requiring manual initiation.
• The job involves SQL commands to create or replace functions within the database which are pivotal to the registration and update of tasks in the dbWatch system, handling tasks more efficiently, and avoiding inconsistencies.

Tables and SQL Execution Details

The job includes SQL operations such as:

• Creating or replacing the ‘framework’ function in the PostgreSQL intended for keeping the execution details of tasks updated.
• Registration or updating of tasks in the ‘dbw_tasks’ table based on the existence and versioning of tasks.
• Updating the ‘dbw_tasks’ table post checking to reflect changes made to tasks as pertained to the company details (changing company to ‘dbwatch.com’ for the ‘SQL statistics’ task).

Integration with Database Tasks

• The framework job is tied to a structured query system that interacts directly with various tables (like ‘dbw_tasks’) providing functionalities including registering new tasks, inserting or updating task parameters, and more.
• Example SQL structure provided in the job execution codes allows for conditional operations based on the existence or the requirements of updating tasks reflecting in these tables.

Dependencies and Cleanup

• This job has specifically declared a dependency on the ‘framework’ itself, ensuring that it cannot execute without the framework being active and correctly functioning.
• Clean-up actions are specified to be true on failure, indicating that any changes or partial updates are rolled back to maintain database integrity upon unsuccessful execution.

Scheduled Reports and Presentations

• Reports generated by this job are structured to create documented outputs in tables based on data fetched from ‘dbw_tasks’ about tasks such as task ID, name, last and next run times, and execution details.
• The reports are tailored to provide a user-friendly presentation of data, useful for auditing and monitoring purposes within dbWatch environment.

This structured and automated approach of the dbWatch Control Center in maintaining its core engine framework demonstrates dbWatch’s commitment to reliability and efficiency in managing complex database environments.