Make sure your SQL databases in the cloud stay performant and within the sizing thresholds your business requires. By monitoring the size, you gain awareness and can take actions to keep only the required amounts of data. This will save you money.
With the SQL monitor agent in Integration Manager it is easy to keep track of your SQL Databases in Azure. Today the there are two categories available for monitoring the SQL Databases.
- Size check
- Custom statements
This blog post describes how to monitor size checks using Integration Manager.
SQL Monitor Agent
With Integration Manager comes an agent for monitoring SQL Server instances and databases on premise and SQL Databases in the cloud. To read more about the agent and see all supported monitoring capabilities, please visit the Documentation site.
The Agent can be installed in multiple instances on premise or in the cloud/partner location on a virtual machine.
Using Remote Configuration the agent can be configured to monitor one or more databases
Size Check Category
Configure the thresholds for the size check category to get warnings and errors if the limits are reached. An error will also be raised if the resource is unavailable (network error, someone accidently removes the database, changes permissions and so on).
There are two options available for the size check evalution
- Size in Megabytes
Read more about configuration in the Integration Manager Documentation, Azure – SQL Size Checks.
When the configuration is done it is easy to add the resource to one or more Monitor Views. Within the monitor view you can configure whether an alert should be raised or not when an error or warning occurs. More about Monitor Views in Integration Manager can be found here.
This screen shot shows a list of my Monitor Views.
The Azure SQL Monitor view, which supervise the size of the databases are currently OK in the example above. The other view, ‘Azure LogicApps Monitor’ indicates a problem with my Logic Apps (more about monitoring Logic Apps in a future blog post).
A specific resource can easily be reconfigured and information about limits are also showed. In the example below one can see that there was indeed a size limit on just 100 MB and percentage was the better monitoring configuration for this specific database.
With Integration Manager it is easy to monitor all your assets independent of where and what they are. This was a short blog post about how to monitor your Azure SQL Databases without logging in to the Azure portal and manually keep track of the size. A database cannot grow beyond limits and your business critical applications will fail if there’s not enough free space to deal with your transaction needs. Stay proactive using Integration Manager