Control Center Jobs Description
Availability
Agent Jobs Check Checks whether there exists jobs on the SQL server which have not been executed, or have failed during execution.
Check database recovery mode Checks if all databases run in SIMPLE (or FULL) recovery mode.
Collation check Checks if there is a collation conflict with temp tables and table variables.
Database backup This procedure analyzes the backup statistics (type D and I) from the msdb.dbo.backupset table (excluding the system databases: master, model and msdb).
Database backup (SIMPLE) This procedure analyzes the backup statistics (type D) from the msdb.dbo.backupset table for databases in SIMPLE recovery model (excluding the system databases: master, model and msdb).
Database backup (system databases) This procedure analyzes the backup statistics for the system databases (master, model and msdb) using data from the msdb.dbo.backupset table.
Database Log backup This procedure checks the database transaction log backups from the msdb.dbo.backupset table (excluding system databases: master, model and msdb).
Database Server uptime Collects database server uptime statistics.
Database status Checks if all databases have status ONLINE
Deadlocks event collector Collects deadlocks event statistics from Microsoft SQL Server Extended Event Log files. If configured a warning or an alarm can be triggered when a deadlock is detected.
Instance error log Reads and checks the Instance error log file by using the sp_readerrorlog stored procedure.
Instance status This alert checks if the instance has been restarted since the last check
Program status Checks for any program connected to the SQL Server by checking the program_name column in the master.dbo.sysprocesses table.
Restricted Enterprise edition features Checks if there are any restricted features in use (supported only by Enterprise or Developer SQL Server edition).
SQL Server Agent status Checks if the SQL Server Agent is running.
Capacity
Auto growth event collector Collects statistics on how often an auto-growth event has occurred.
Data file size check Checks the remaining space for all databases where the data files are set with limited growth rate (max size not unlimited).
Database disk capacity Checks free space on drives where data and transaction log files are defined. An alarm (or warning) is raised if the percentage limit is reached OR if the abosulte limit is reached. IF the xp_cmdshell Instance configuration option is enabled the alert can check disk and mounted volumes where data-files are not present.
Database disk space usage Checks free space on drives where all data and transaction log files are defined. Drives where no data files exist will be ignored.
Database growth rate (aggregated) Collects size of all database files (including transaction log files) to visualize the growth rate for all databases.
Database growth rate (detailed) Collects size of database files (including transaction log files) to visualize the growth rate for the largest databases.
Databases NOT IN USE collector Collects information about most inactive databases.
Disk space check Checks the amount of free space on the available disk drives.
Filegroups growth rate This procedure collects space usage in all filegroups defined in each database. The undocumented “sp_MSforeachdb” Stored Procedure is used to execute T-SQL statements against dbo.sysfiles table in every database defined on a SQL Server instance.
Instance error log file size check Checks the size og the Instance error log file by using the extended stored procedure xp_cmdshell.
Objects size collector (all databases) Collects table and index size information for the largest objects for all databases.
Temporary database space usage Checks space usage in tempdb database, and collects statistics including size of data and transaction log files.
Transaction log size check This procedure checks the size of the transaction log (log file(s) size), and compares it to the database size (data file(s) size). If the size of the transaction log file(s) in percentage is greater than the warning/alarm parameter value, the check returns a warning/alarm.
Transaction log space usage This procedure checks information returned by DBCC SQLPERF which is used to monitor the amount of space used in the transaction log.
Clustering and Replication
Database mirroring Checks state information of all mirrored databases.
Log shipping monitor (primary) Monitor the primary database in each log shipping configuration, including information about the last backup file and last restored file.
Log shipping monitor (secondary) Monitor the secondary database in each log shipping configuration.
Replication status The following check provides general info in regards to any replication going on in a server.
Maintenance
Autogrow settings Checks database files auto-growth settings.
Backup All databases Takes backup of all application and system databases.
Backup All transaction logs Takes backup of all transaction logs for databases running in FULL recovery mode.
Check database and server principal mapping Checks if the database owner (dbo) is maped into any Server Login (server principal).
Cleanup MSDB history tables This task deletes entries in the MSDB database history tables which holds statistics of backup/restore, jobs and maintenance plan executions.
Cycle error log This task cycle MS SQL Server error log and Agent error log files.
DBCC CHECKDB Checks the logical and physical integrity of all the objects in all databases by performing the DBCC CHECKDB operation.
DBCC UPDATEUSAGE This task is performing the DBCC UPDATEUSAGE operation to corrects pages and row count inaccuracies in the catalog views. These inaccuracies may cause incorrect space usage reports returned by the sp_spaceused system stored procedure.
framework dbWatch engine framework job (for internal use only). Used for patching or upgrading of dbWatch engine framework.
Internal fragmentation check Checks the internal fragmentation for tables and indexes in all databases. The information is extracted from the dynamic management function (view) sys.dm_db_index_physical_stats.
Rebuild indexes Rebuilds fragmented indexes in all databases.
Rebuld indexes in table Rebuilds fragmented indexes in all tables listed in the “table list” parameter.
Reorganize indexes Reorganizes fragmented indexes in all databases.
Reorganize indexes in table Reorganizing fragmented indexes in all tables listed in the “table list” parameter.
SQL Server performance counters Checks if SQL Server performance counters are missing.
Update index statistics Update statistics in all (non-system) databases.
Update statistics Update statistics in all (non system) databases.
Performance
Blocking statistics Checks whether there exists any blocked sessions.
Data cache memory usage Collects data cache memory usage per database (for top 10 databases).
Data hit ratio Monitors the buffer cache hit ratio by extracting counter values from the master.dbo.sysperfinfo table for the counters “Buffer cache hit ratio” and “Buffer cache hit ratio base”.
File IO statistics Collects I/O statistics for data and log files.
High activity monitor Collects SQL instance CPU usage, CPU usage of other processes, logical and physical reads, and active processes count on the SQL Server instance.
Index usage statistics (all databases) This procedure collects statistics from sys.dm_db_index_usage_stats performance view which gives information on how an index (or a table – heap) has been used to resolve queries.
Instance memory check This job checks the target memory value of the SQL Server instance, and gives a warning/alarm if the instance is not able to allocate a certain percentage of the total server/machine memory.
Instance memory usage Collects total memory usage and data cache memory usage for SQL Server instance. This dbWatch task can be configured to automatically reduce the amount of memory used by the SQL Server instance.
Internal fragmentation (all databases) Internal fragmentation occurs when there is too much free space in the index pages. Typically, some free space is desirable, especially when the index is created or rebuilt. You can specify the Fill Factor setting when the index is created or rebuilt to indicate a percentage of how full the index pages are when created. If the index pages are too fragmented, it will cause queries to take longer (because of the extra reads required to find the data set) and cause your indexes to grow larger than necessary. If no space is available in the index data pages, data changes (primarily inserts) will cause page splits, which also require additional system resources to perform.
Lazy writer and Checkpoint statistics Monitors “Checkpoint pages/sec”, “Lazy writes/sec” and “Page life expectancy” by extracting counter values from the sys.dm_os_performance_counters performace table.
Session load Shows the number of active sessions over time.
Sessions per database This task returns aggregate performance statistics based on sessions connected to the SQL Server instance.
SQL statements (Logical reads) Collects statistics for the SQL statements corresponding to the query plans that have resulted in the most logical reads.
Test DML-DDL performance Runs performance test on the database. The procedure executes SELECT, INSERT, UPDATE, DELETE (and TRUNCATE) statements on the test table.
Transactions load Shows the transactions load over time, total and top 5 databases.
Transactions log flushed bytes load Shows bytes flushed to transaction logs over time, total and top 5 databases.
Wait statistics Collects statistics about all waits encountered by threads that executed. This task is based on the sys.dm_os_wait_stats dynamic performance view.

← For MySQL and MariaDB / For Postgres →

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment