Consolidation of BizTalk Server Databases

A Microsoft BizTalk Server installation may require the creation of up to 13 separate databases in Microsoft SQL Server for use as data stores for various BizTalk Server features. Due to the overhead required to manage and maintain this many databases, BizTalk Server accommodates the consolidation of several of these databases into a single database. This section describes how to accomplish BizTalk Server database consolidation and discusses considerations for implementing BizTalk Server database consolidation.

noteNote
For a complete list of all of the databases that are required when installing BizTalk Server, see the BizTalk Server 2009 Installation and Upgrade Guides available at http://go.microsoft.com/fwlink/?LinkId=128383.

Implementing BizTalk Database Consolidation

BizTalk Server database consolidation is performed after installing BizTalk Server, during BizTalk Server configuration. Follow these steps to implement BizTalk Server database consolidation:

  1. Click Start, point to Programs, point to Microsoft BizTalk Server 2009, and then click BizTalk Server Configuration to start BizTalk Server 2009 Configuration. If prompted to select a configuration type choose the option for Custom configuration.

  2. Specify the same SQL Server Server Name and Database Name (for example BizTalkConsolidatedDb) for one of more of the following data stores:

     

    Feature Name Data Store Name

    Enterprise SSO

    SSO Database

    Group

    BizTalk Management Database

    Group

    BizTalk MessageBox Database

    Group

    BizTalk Tracking Database

    Business Rules Engine

    Rule Engine Database

    Note that the following data stores should not be configured to share a SQL Server database:

     

    Feature Name Data Store Name

    BAM Tools

    BAM Primary Import Database

    BAM Tools

    BAM Archive Database

  3. Set the remaining configuration options and apply the configuration. The configuration tool will create tables in the shared SQL Server database for the data stores for which you specified the same SQL Server Server Name and Database Name.

Considerations for Implementing BizTalk Database Consolidation

When consolidating a BizTalk Database, consider the following:

  1. Database consolidation reduces the overhead associated with managing and maintaining the BizTalk Server databases but should only be implemented in the appropriate environment. Before implementing BizTalk Server database consolidation in a production environment, the effect on BizTalk Server sustained performance should be measured in a staging environment. Consider implementing BizTalk Server database consolidation to simplify database administration and maintenance in the following scenarios:

    • Small scale, low volume BizTalk Server production environments where database performance is very unlikely to become a performance bottleneck.

    • Medium scale, medium volume BizTalk Server production environments if the BizTalk tracking database is not included in the consolidation and, ideally, if the BizTalk tracking database is created on a separate physical disk from the consolidated database.

    • Large scale, high volume BizTalk Server production environments if the shared SQL Server database is physically located on a very high performance storage area network (SAN) device where the likelihood of the database becoming a performance bottleneck is very low.

    • Proof of concept or development environments where database performance is of secondary concern.

  2. Overall BizTalk Server performance is usually dependent upon the performance of the BizTalk Server databases. Therefore database consolidation should not be implemented in any BizTalk Server production environment that is experiencing or will be experiencing high volume. One exception to this is if the BizTalk Server databases are located on a very high performance storage area network (SAN) device where the likelihood of the database becoming a performance bottleneck is very low.

  3. If the BizTalk Server Management database is included in the database consolidation and the consolidation database is not named BizTalkMgmtDb, then the BizTalk Administration console must be configured to point to the consolidation database. Follow the steps in How to Connect to an Existing Group and configure the BizTalk Server Administration console to point to the consolidation database in order to manage the BizTalk Server group.

  4. For more information about sustainable BizTalk Server performance, please refer to Planning for Sustained Performance.

For more information about activities related to maintaining the BizTalk Server databases, please refer to Maintaining BizTalk Server.

  © 2009 Microsoft Corporation. All rights reserved.
Show: