Database growth rate (detailed)
Job details
Name: | Database growth rate (detailed) |
Platform: | Mariadb |
Category: | Capacity |
Description: | Collects detailed growth rate information. |
Long description: | Collects detailed information on the growth rate of the database server (detailed). |
Version: | 2.1 |
Default schedule: | 10 5,17 * * |
Requires engine install: | Yes |
Compatibility tag: | .[type=‘instance’ & is_mariadb_branch=‘1′]/.[hasengine=‘YES’] |
Parameters
Name | Default value | Description |
---|---|---|
min histr interval | 360 | The minimum number of minutes before a new history record will be collected in the history table. |
Job Summary
- Purpose: The purpose of this job is to systematically collect and analyze the growth rate of databases, focusing particularly on the largest databases within a MariaDB environment. By tracking these metrics, significant changes in storage and database size can be identified proactively.
- Why: Monitoring the database growth rate is crucial for capacity planning and resource allocation. By understanding which databases are growing fastest, system administrators can predict when additional resources or optimizations might be needed, ensuring that the system performs optimally without unexpected disruptions.
- Manual checking: In order to check the database growth rate manually, the following SQL commands can be run within the database:
SELECT schema_name, SUM(data_length + index_length) AS Total_Size FROM information_schema.tables GROUP BY schema_name ORDER BY Total_Size DESC;
Job Details
Dependencies
The task depends on specific tables and procedures that are part of its mechanism:
- Database growth rate detailed calculation
- Database size historical detail tracking
- Ranking of databases by size for concise reporting
Dependency Object | Description |
---|---|
database_growth_rate_det | Self-referencing dependency for task management |
dbw_db_size_histr_det | Historical data collection table for database sizes |
dbw_db_size_histr_det_rank | Provides a ranking of databases based on size in a historical context |
Implementation Logic
The key operations performed by the job on execution include:
- Creation of tables to track detailed size metrics and rankings of databases.
- A procedure that iterates over all databases, collecting and updating historical size data.
- Ranking the top databases by size for targeted reporting.
- Calculation and reporting of the largest database’s size and preparing detailed execution metadata.
Scheduled Execution
This task is typically scheduled to run twice daily, specifically at 05:10 and 17:10 server time, ensuring that growth trends are captured with sufficient granularity to be actionable.
Output and Reporting
The output of this job includes detailed reports on database sizes, which are tracked over time and displayed both in tabular and graphical formats. The default report includes:
- Listings of the top databases by size, with updates on their growth over recorded intervals.
- Charts visualizing growth trends, focused on the largest few databases, providing clear visual indications of growth patterns and anomalies.
Report Element | Description |
---|---|
Aggregation type | Lists the type of data aggregated, specifically database names |
Size | Sizes of databases presented in Megabytes (rounded off) |
History date | Specific dates when the data size recordings were taken |
This structured approach to monitoring facilitates effective data governance and operational planning, essential in managing considerable database environments efficiently.