BizTalk database sizing statistics

In the hope that this might help someone who is tasked to estimate the size of BizTalk Server 2006 databases, I’m offering a few statistics.

These statistics comes from an engagement that uses very few orchestrations and more or less does messaging only – ie do all the work in pipeline components and/or maps. Just to give you a hint of the volumes we are talking about – here are some numbers from the beginning of May:

Now we have only been doing the volumes specified in the above table for roughly two months, before that is has been smaller but incrementally increasing (it would too drawn out to give the full story). I know that gives you a somewhat incomplete background, but that’s just how it is. Here are the sizes of the base BizTalk Server databases (all figures are in MB).

I guess I should also mention that we have the BizTalk backup jobs doing full backups on a daily basis, as well as trasaction log backups every 20 minutes, and the DTA purge and archive setup for 12 live hours and 7 hard days. We have roughly about 300 receive ports, 1000 receive locations and 400 send ports and 20 or so orchestrations. Regular BizTalk Tracking hasn’t been globally turned off, but is at a basic minimum. A BAM Tracking component does the real tracking as far as monitoring goes.

Do you have any statistics that you could perhaps share with me?