Data Purging
  • 03 Dec 2020
  • 1 Minute to read
  • Dark
  • PDF

Data Purging

  • Dark
  • PDF

Article summary

In its database, BizTalk360 collects and stores multiple types of data. Think of for example Event Log entries, Performance Monitor counters, but also Auditing information and Alert/Maintenance History. To prevent that the BizTalk360 database becomes too big, BizTalk360 comes out-of-the-box with the ability to set purging duration and the background monitoring service has the capability to purge older data automatically after a specified period. The Administrators/Super users can set up the Purge duration' under 'Settings'. Follow the steps as shown below to set up the data purging policy:

  • Log in to the BizTalk360 application (as Super user)
  • Click the 'Settings' icon in the left menu bar
  • Expand 'BizTalk360 Health' from the menu options
  • Click 'Data Purging' from the list of options
  • Customize the purging policies by selecting the count and day/week/month options from the list boxes
  • Click 'Save' to save the data purging policies

Large Data Growth In BizTalk360 Database

How to find out whether you are affected?

  • Open SQL Server Management Studio, right-click on the BizTalk360 database
  • Navigate to Reports > Standard Reports > Disk Usage by Top Tables. You will see a report as shown below:


If you see the record count in some unusual numbers like over 1 million records, then you are affected. It is important to correct this situation, else you will quickly run out of disk space.

How to solve it?

Out of the box, BizTalk360 comes with its own routines to clean up the data based on the purging settings (in the UI under Settings > BizTalk360 Health > Data Purging).

The first suggestion is to reduce the number of days you want to keep specific data. This way, the amount of data in the database will be reduced.

To manually purge the database in case of large database growth, you can use the stored procedure 'sp_b360_admin_CleanupDB'.

When the number of records in the database grow quickly, the call to the stored procedure(s) can start to get timed out from the monitoring services. This will result in data not being cleared and resulting in unusual database growth. We have published a best practices white paper. If in case you missed it, please take a look

Was this article helpful?