Skip to content

Latest commit

 

History

History
62 lines (42 loc) · 7.42 KB

consolidate-the-biztalk-server-databases2.md

File metadata and controls

62 lines (42 loc) · 7.42 KB
Raw
description title ms.custom ms.date ms.service ms.reviewer ms.suite ms.topic
Learn more about: Consolidate the BizTalk Server Databases2
Consolidate the BizTalk Server Databases2
06/08/2017
biztalk-server
article

Consolidate the BizTalk Server Databases2

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

Note

For a complete list of all of the databases that are required when installing [!INCLUDEbtsBizTalkServerNoVersion], see Databases in BizTalk Server.

Implementing BizTalk Database Consolidation

[!INCLUDEbtsBizTalkServerNoVersion] database consolidation is performed after installing [!INCLUDEbtsBizTalkServerNoVersion], during [!INCLUDEbtsBizTalkServerNoVersion] configuration. Follow these steps to implement [!INCLUDEbtsBizTalkServerNoVersion] database consolidation:

  1. Click Start, point to Programs, point to [!INCLUDEbtsBizTalkServerNoVersion], and then click BizTalk Server Configuration. If prompted to select a configuration type, click Custom configuration.

  2. Enter the same [!INCLUDEbtsSQLServerNoVersion]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 [!INCLUDEbtsSQLServerNoVersion] 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 [!INCLUDEbtsSQLServerNoVersion] database for the data stores for which you specified the same [!INCLUDEbtsSQLServerNoVersion]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 [!INCLUDEbtsBizTalkServerNoVersion] databases but should only be implemented in the appropriate environment. Before implementing [!INCLUDEbtsBizTalkServerNoVersion] database consolidation in a production environment, the effect on [!INCLUDEbtsBizTalkServerNoVersion] sustained performance should be measured in a staging environment. Consider implementing [!INCLUDEbtsBizTalkServerNoVersion] database consolidation to simplify database administration and maintenance in the following scenarios:

    • Small scale, low volume [!INCLUDEbtsBizTalkServerNoVersion] production environments where database performance is very unlikely to become a performance bottleneck.

    • Medium scale, medium volume [!INCLUDEbtsBizTalkServerNoVersion] 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 [!INCLUDEbtsBizTalkServerNoVersion] production environments if the shared [!INCLUDEbtsSQLServerNoVersion] 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 [!INCLUDEbtsBizTalkServerNoVersion] performance is usually dependent upon the performance of the [!INCLUDEbtsBizTalkServerNoVersion] databases. Therefore database consolidation should not be implemented in any [!INCLUDEbtsBizTalkServerNoVersion] production environment that is experiencing or will be experiencing high volume. One exception to this is if the [!INCLUDEbtsBizTalkServerNoVersion] 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. If the database disks are not housed on a high performance SAN, distributed databases provide superior performance to consolidated databases, especially under load.

  3. If the [!INCLUDEbtsBizTalkServerNoVersion] 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 [!INCLUDEbtsBizTalkServerNoVersion] Administration console to point to the consolidation database in order to manage the [!INCLUDEbtsBizTalkServerNoVersion] group.

  4. For more information about sustainable [!INCLUDEbtsBizTalkServerNoVersion] performance, please refer to Planning for Sustained Performance.

    For more information about activities related to maintaining the [!INCLUDEbtsBizTalkServerNoVersion] databases, please refer to Maintaining BizTalk Server1.