Werk #18497: mssql_datafiles, mssql_transactionlogs: fix incorrect maximum size
| Component | Checks & agents | ||||||
| Title | mssql_datafiles, mssql_transactionlogs: fix incorrect maximum size | ||||||
| Date | Jun 30, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Compatible - no manual interaction needed | ||||||
| Checkmk versions & editions |
|
The MSSQL data file and transaction log checks report a maximum size, which is used as the reference value for the configured levels and for the graph boundaries. This value was calculated incorrectly in several situations.
- The room a file could grow into was based on its currently used size plus the free filesystem space. Since a file already occupies its full allocated size on the filesystem, the maximum size was understated. It is now based on the allocated size plus the free filesystem space, capped at the maximum database file size configured in the database server.
- When several database files shared a filesystem, only the first file was credited with the available free space; the others were treated as if the filesystem were full. The free space is now shared correctly among all files on the same filesystem.
- If a service summarizes several files and one of them could grow without limit, all files evaluated after it were treated as unlimited too. Unlimited growth is now evaluated per filesystem.
Because the maximum size is the reference for the configured levels and graph boundaries, affected services may now report a different maximum size and, accordingly, different WARN/CRIT results.
In most cases the maximum size increases, so services with percentage levels go WARN or CRIT later than before. If you rely on these levels, review the rules MSSQL datafile sizes and MSSQL transactionlog sizes.
When the configured maximum cannot be reached due to insufficient free filesystem space, the service now shows a notice that the maximum is capped at the available filesystem space.