- 5 minutes to read

Managing SQL Server Database Size Checks

This monitoring feature helps you get alerted when the size of your SQL Databases grow out of your control and/or the database is unavailable

The Database Monitoring Agent monitors the size of configured SQL Databases. Each monitored database is represented in Nodinite as 1 Resource. Each SQL Database returns its evaluated state which therefore can be monitored from the use of Monitor Views and external alerts can be pushed using any of the installed : Alarm Plugins.

The main difference compared to Azure SQL Database Size Checks is that there is also a transaction log to monitor for SQL Databases.

Size checks for SQL Databases are grouped by the Category SQL Size Checks (global) and SQL Size Checks - Specific.

Category - SQL Size Checks
Example of a Monitor View filtered by the 'SQL Size Checks' and 'SQL Size Checks - Specific'

  • Your SQL Size Checks within the SQL databases(s) are listed in Nodinite as resources where the name of the SQL Database becomes the Resource name.
graph LR subgraph "Configuration" c["fal:fa-code 1 SQL Database"] --> r[fal:fa-lightbulb 1 Resource] end

What are the key features for Monitoring SQL Database Size Checks?

  • State Evaluation - Monitors and evaluates the state
  • Actions - Support for the execution of Remote Actions

What is evaluated for SQL Database Size Checks?

The different possible evaluated states for your SQL Database are provided in the table below:

State Status Description Actions
Unavailable Resource not available Evaluation of the 'Database size' is not possible either due to:
  • network or security-related problems
  • A specific configuration exists with a database that no longer exists
Review prerequisites
Error Error state raised The database size is above the error threshold value Edit
Warning Warning state raised The database size is above the warning threshold value Edit
OK Online SQL Job is valid, executes and reports that no problems were detected Edit

TIP: The evaluated state may be reconfigured using the Expected State functionality that exists on every Resource within Nodinite.


How do I configure the thresholds for SQL Database Size Checks?

SQL Database Size Checks are enabled when the checkbox Enable SQL database monitoring is checked from within the Remote Configuration dialogue for the Database Monitoring Agent. When checked, the database provided by the ConnectionString is monitored.

There are two different ways to configure thresholds for SQL Jobs:

  1. Global configuration
  2. Specific configuration

The main differences between the SQL Size Checks and the SQL Size Checks - Specific are:

  • Global default threshold values are used in SQL Size Checks
    • Applies to all non-specific databases
    • Changes does not in any way interfere with any specific settings
  • Customized threshold values are used in SQL Size Checks - Specific
    • Applied on only one (1 specific) database
    • Changes does not in any way interfere with global settings

Global configuration

From the SQL databases tab, you can manage the global settings. You then need to click on the Size check tab.

Global Configuration Example of the Size check tab with global monitoring thresholds for size related checks.

You can then edit the available properties.

  • Database Size
    • Warning: Allowed size before state evaluates as Warning
    • Error: Allowed size before state evaluates as Error
  • Transaction Log Size
    • Warning: Allowed size before state evaluates as Warning
    • Error: Allowed size before state evaluates as Error

The Application - is inherited from the SQL Database Instance being configured.

Specific configuration

Managing specific SQL Jobs is covered in the Edit thresholds remote action section below.


Actions

The Database Monitoring Agent category SQL Size Checks has support for the following Remote Actions:

Remote Actions

Edit thresholds

Click on the Edit thresholds menu item in the Actions button to manage the specific Monitoring thresholds.

Edit thresholds Action menu item

Then, The following dialogue displays.
Edit thresholds
Example of dialogue changing global thresholds to specific thresholds.

The Default values are set using Remote Configuration. Review the Global Configuration section of this document for further details.

The same properties as described in the Global configuration are available and in addition the following can be managed:

  • Application - a way of grouping resources (by default the Application used for the SQL Instance is re-used)
  • Description - Short description for this specific size check

Shrink

New 6.1.0.0 If the Service account in use by the Monitoring Agent, the end-user may successfully invoke a background task and run a DBCC SHRINKDATABASE (%databasename%) command.

Click on the Shrink menu item in the Actions button to manage the invoke the background operation.

Shrink menu item Action

Next, the end-user is prompted with intent:
Confirm Shrink Operation
User must confirm intent to proceede with the Shrink operation.

Invocation operation may succeed, make sure to review the diagnostics log to verify successful completion. If you open the Edit thresholds modal, you should see a decrease in allocated space after waiting. The operation may take some time to complete depending on the amount of data to deallocate.

Save

You must click on the Save button or click on the Save and close button for any changes to be written to the agent and take effect on next synchronisation.
Save and Close buttons

NOTE: Depending on the synchronisation interval set for the agent, there might be a delay before the Web Client reflects upon the change. You can choose to force the agent to synchronize from the configuration of the Monitoring Agents.

Save and close, save, and close the dialogue.

Cancel, close the dialogue without saving any changes.


Next Step

Add or manage Monitor View

Azure - SQL Size Checks
Database Monitoring Agent
SQL Categories
Resources
Monitoring Agents
Monitor Views