Managing SQL Server Database Size Checks
Info
On this page you will learn how to get alerts 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.
The Size check Monitoring for SQL Databases group Resources by the Category SQL Size Checks:
Here's an example of a Monitor View filtered by the 'SQL Size Checks'.
- 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.
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:
|
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 System Administrator can override the Monitoring state using the Expected State feature on the 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:
Global configuration
From the SQL databases tab, you can manage the global settings. You then need to click on the Size check tab. Here's an example of the Size check tab with global monitoring thresholds for size related checks.
You can then edit the available properties.
- Enable Database Size Check Monitoring - When checked, Monitor the size of databases
- 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
Actions
The Database Monitoring Agent category SQL Size Checks has support for the following Remote Actions:
- Edit thresholds
- Shrink New 6.1.0.0
Edit thresholds
Click on the Edit thresholds menu item in the Actions button to manage the specific Monitoring thresholds.
Then, The following dialogue displays.
Here's an example of dialogue changing global thresholds to a specific threshold.
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:
- 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.
Next, the end-user is prompted with intent:
User must confirm intent to proceed 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 'Save' or 'Save and close' for changes to persist. The new settings/thresholds are evaluated on the next synchronization.
Here's an example of the Save options.
Note
Depending on the synchronization interval set for the agent, there might be a delay before the Web Client reflects upon the change. You can force the agent to synchronize the Configuration for all Nodinite Monitoring Agents.
Save and close, save, and close the dialogue.
Cancel, closes the dialogue without saving any changes.
Next Step
Related
Azure - SQL Size Checks
Database Monitoring Agent
SQL Categories
Resources
Monitoring Agents
Monitor Views