Engine jobs - Control Center - 1.0

About dbWatch Control Center
- Release notes
- Find your version
- Platforms supported
Getting Started
- Installing on Windows
- Installing on Linux
  - Console installation on Ubuntu
- Initial Domain Setup
- Multi-server setup
Product Overview
- Architecture
  - Example architecture designs
  - Cloud router
    - Cloud router security
- File Structure
- Network and communications
- Database operations philosophy
- Monitor dashboards and overview screens
Installing and using premium packages
- SQL Performance package
- Security and Compliance package
  - Installation of the Security and Compliance package
  - Security and Compliance package on SQL Server
- Automated maintenance package
Using Control Center
- The modules of Control Center
- Disabling and Enabling Views
- Instance management
- Domain Configuration
- Monitoring
- Management
  - Management on SQL Server
- Worksheet
- Autodiscover
  - Discovering Database Instances
    - Defining Autodiscover Ports
    - Auto-discover with different default port
- FDL console
- Reporting
Customization
- Importing resources
- Monitoring
- Property System
- Management
- Reports
- Extensions and 3rd party integrations
  - Email and SMS
    - Configuring email extension for Service Now
- Web server
Advanced Topics
- FDL – Farm Data Language
  - Functions
  - Available properties
- Application Modules
  - Unit4 Agresso
- The FString format
- Product Security
- Auditing
- Control Center Commandline
- Exporting configuration from 12 to CC
- Internal Control Center firewall
Troubleshooting Guide
- Backup of dbWatch
- Adding MySQL Instance with Super Privilege Error
- Restore configuration backup
- Issues and troubleshooting
- Definition Mapping
- Resetting dbWatch Control Center Admin Account
- Fresh Installation of dbWatch Control Center
- Remote Support
Additional Resources
- Database Farm Management Additional Resources
Licensing terms

Download as PDF

Engine jobs

Each engine Job consists of a set of objects (procedures, tables, etc) that are installed on the monitored database instance. The main procedure will be triggered by the dbWatch Server, This procedure will then perform a check or collect statistics regarding the instance and typically put data in a table that can be reported on later.

All Jobs provided by dbWatch are provided as open source. This is part of the dbWatch philosophy of mixed source. Customers are able to (and indeed we recommend) that they change the standard supplied jobs. By using our codes as the basis for their own customized ‘developments’. They can then customize their jobs to suit their specific needs. dbWatch Software Support is available to assist with customized developments.

← Job types / No-engine jobs →

Feedback

Post your comment on this topic.