BizTalk Admin & Disaster Recovery

Well our BizTalk Server tracking database was growing large and the Job that was configured to purge and Archive was not running well.

Use the following to purge.

–– Change to the BizTalk Tracking database.

USE BizTalkDTADb

GO

–– Purge tracking data older than two hours.

DECLARE @dtLastBackup DATETIME

SET @dtLastBackup = GetUTCDate()

EXEC dtasp_PurgeTrackingDatabase 2, 0, 1, @dtLastBackup

Read more: http://www.modhul.com/2008/04/13/why-archive-and-purge-when-you-can-just-purge/#ixzz2CPSaXMDB

As I started executing this statement. It took a while and I could notice the drastic change in my BiztalkDTADb_log.ldf located it C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA.

It has started to grow to almost the size of my mdf file. When I thought it was done, Damn!! By log file grew out of the max limit size and threw an error.

Well, We would have to work on this task again.

Additionally, this article explains in detail on how to truncate tracking database.

http://www.modhul.com/2008/04/10/truncating-the-biztalk-2006-tracking-database/

If you ever want to plan for Disaster recovery, consider reading this article

http://www.modhul.com/2009/06/29/configuring-biztalk-for-disaster-recovery-part-1/

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s