framework
Job details
Name: |
framework |
Platform: |
Sqlserver |
Category: |
Maintenance |
Description: |
dbWatch engine framework job (for internal use only). Used for patching or upgrading of dbWatch engine framework. |
Long description: |
dbWatch engine framework job (for internal use only). Used for patching or upgrading of dbWatch engine framework. |
Version: |
2.81 |
Default schedule: |
50 5 1 * |
Requires engine install: |
Yes |
Compatibility tag: |
.[type=‘instance’ & databasetype=‘sqlserver’]/instance[maj_version > ‘2000′ & hasengine=‘YES’ & engine_edition = ‘Microsoft SQL Server’] |
Parameters
Name |
Default value |
Description |
delete future date records |
NO |
It is possible that the clock on the database server may be set incorrectly, for example far into the future. In such cases, dbWatch jobs will collect statistics that have the wrong date. By setting this parameter to YES, the procedure will remove these records. This only applies if the clock on the server has been moved forward in time. |
Job Summary
- Purpose: The purpose of this job is to maintain and update the dbWatch engine framework by performing tasks like patching or upgrades.
- Why: This job is crucial for ensuring the dbWatch engine remains efficient, secure, and updated with latest changes, thereby enhancing overall system performance and reliability. Failure to update or maintain can lead to system vulnerabilities or operational inefficiencies.
- Manual checking: Manual checking can be done by querying the database to check the versions and configurations of the engine framework:
select 'dbWatch Framework 2.81 installed' as version
Dependencies and Cleanup Details
- This job has several dependencies, mainly on internal framework objects and tables used by dbWatch to monitor and manage database environments.
- Cleanup processes are activated upon failure to ensure system stability and data integrity.
Object |
Object Type |
Description |
Cleanup on Fail |
framework |
2 |
Main framework task dependency on itself |
true |
dbw_framework_tab_info |
0 |
Holds framework table details |
false |
dbw_days_fw |
0 |
Table to hold day numbers |
true |
dbw_hours_fw |
0 |
Table to hold hour numbers |
true |
dbv_w_histr_fw |
1 |
View showing weekly history warnings |
true |
dbv_a_histr_fw |
1 |
View showing alert history |
true |
dbw_framework_tab_del_histr |
0 |
Deletes date history table |
true |
Enhancements and Upgrades
Upgrades and modulations occur for several versions from 1.9 to the latest release, which involves:
- Updating task names and parameters related to security and maintenance.
- Creating or modifying database objects such as tables and views essential for task operations.
- Special procedures are defined to ensure data consistency and accuracy, especially concerning date and time settings that could potentially register future-dated records mistakenly due to clock settings.
Framework Check Operations
- The procedure involves a series of checks for datetime data types and records with dates that could be ‘in the future’ due to incorrect system clock settings.
- It performs deletions and updates based on parameter settings that control whether future-dated records should be removed.
- Each operational step is closely monitored, and a comprehensive update is made to the task values to reflect the actions taken during the job execution.
Reporting
- Framework Version: Indicates the current installed version of dbWatch Framework.
- Tables with Date Columns: Lists all dbWatch tables containing date columns along with records flagged with future dates and those modified during the last execution.
- Delete History: Details which tables from which records with incorrect future dates were removed.
In summary, this monitoring job in dbWatch Control Center plays a vital role in maintaining the system’s integrity and operational functionality by regularly updating and checking the framework configurations and database environment.