Data Purge in BizTalk360
- Updated on 16 Nov 2018
- 1 minute to read
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 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 application (as Super user)
- Click the Settings icon at the top of the page
- Click BizTalk360 Health from the left menu bar
- Click Data Purging from the list of options
- Customize the purging policy by selecting the count and day/week/month options from the list boxes
- Click Save to save the data purging policy
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's important to correct this situation, else you will quickly run out of disk space.
How to solve?
Out of the box, BizTalk360 comes with it's own routines to clean up the data based on the purging settings (in the UI under Settings > BizTalk360 Health > Data Purging).
First suggestion is to reduce the number of purge days. So that the data will be reduced.
Until v5.0, we called a single stored procedure (sp_b360_admin_PurgePolicies) from our monitoring service which takes care of all the purging. In v6.0, we improved the logic by splitting it into multiple stored procedures (sp_b360_admin_PurgePolicies) which takes care of various parts of data purging.
For the more recent versions of BizTalk360, you can use the stored procedure sp_b360_admin_CleanupDB to manually purge the database in case of large database growth.
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