Supervise the size of your SQL Databases in Azure

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.

SQL Monitor Agent


Global Configuration

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

  1. Percentage
  2. Size in Megabytes

Remote Configuration SQL Server

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.

Azure SQL Monitor

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).

Detailed configuration

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.

Azure Database Size Check Configuration


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

Videos on  YouTube
Information on  Twitter
Contact on  LinkedIn

Online documentation: Latest version
Latest release notes: Release Notes
Support site: Support Site

Null Adapter – Keep it clean

Tired of receiving unwanted messages in BizTalk?

Responses from ”Solid-Response” send ports or maybe other messages with some kind of status like ”In-Progress” might not be interesting or useful.

One common way to take care of situations like above, is to route them to a send port which writes them to a ”trashcan/dummy” folder” together with a scheduled task job to run a clean-up script every night. The setup is common even in production environments. Without a fully working clean up stored on C: – you have a recipe for disaster.


The solution should be considered as a hack. It can work, but requires attention from BizTalk operators, supervising disk size and changes to the environment (change of permissions, etc.) might have fatal consequences.

Null Adapter from Integration Software to the rescue

If you use our free BizTalk Null Adapter from Integration Software instead, you can easily configure the send port to consume (void) those unwanted messages.


The only sign left of the message is if tracking is enabled or you opt to write to the event-log. Remember to set the event log to cycle, additional information about the event log can be read here.

More information and download.

Installation and Configuration

Extract the files from the downloaded zip file. Run Install.exe:



Answer ‘y’ when promted:



Add the adapter in the BizTalk server:



Configure the Null Adapter in the BizTalk server:



Configure the send port:

Null Adapter - Send Port


It is also possible to write to the local Event Log when consuming messages in the Null Adapter. Note that if you have multiple processing BizTalk nodes the event will be logged locally on the BizTalk server sponsoring the send operation.

Null Adapter - Send Port Configuration


If you have tracking enabled it will show up like this under Tracked Messages:

Null Adapter - Tracked Messages


If the message body is tracked you can of course the message content:

Null Adapter - Message Body

Using the enterprise wide logging capabilities of Integration Manager is a much better option for your logging requirements. The BizTalk tracking database is not designed for long term storage.  Integration Manager is designed for long term archiving with very easy to setup search fields for self service operations. Integration Manager replaces the need for error prone and costly BAM solutions.


Example of a logged message processed by our Null Adapter from within Integration Manager:

Null Adapter - Integration Manager


The content of the logged message:



If you would like to know more about Integration Manager, please feel free to contact us at

Good luck!