Consider the following scenario:
In this scenario, some of these records are under heavy load, and the bts_PurgeSubscription stored procedure does not clear records in the EqualsPredicate2ndPass table. This causes the BizTalk Server MessageBox database (BizTalkMsgBoxDb) to grow very large.
- You run BizTalk orchestrations that result in instance subscriptions in Microsoft BizTalk Server 2010.
- When the instances of the orchestrations are processed, records are generated in the EqualsPredicate2ndPass table.
In this scenario, some of these records are under heavy load, and the bts_PurgeSubscription stored procedure does not clear records in the EqualsPredicate2ndPass table. This causes the BizTalk Server MessageBox database (BizTalkMsgBoxDb) to grow very large.