I’m currently at the MVP Summit at Redmond and ran into a fellow MVP
Alan Smith – he had a nice technique *which is untested in production*. He did
stress it was mainly for a developer machine.

He referred to it a ‘BizTalk Co-Hosting’ which I had not heard it referenced to before.

Co-Hosting (as described by Alan)

What it is:
– condensing the BizTalk databases down to 2 (a BizTalkDB and a SSODB)
– simplier management/backup etc.
NOTE: performance may be an issue here so keep that in mind.

How to do it:
– during the BizTlak Configuration stage, specify the same Database name
for all the databases except SSO (as it doesnt play the game yet)
– this means Management, MsgBoxDB, BAM etc etc etc….
– optionally set the RecoveryModel to simple on
the BizTalk Database such that there are no log files to worry about 🙂

When to use:
– my bet would be on a developer machine where you want to simplify the BizTalk
setup and problems that may arise from multiple distributed transactions with Business
Processes from BizTalk.

Note: We dont need to have ONE BizTalkDB either, we could have TWO
or what ever number you want. e.g. ManagementDB + MsgBoxDB in one, and Tracking +
BAM in the other.