Configuring Biztalk Servers in production

Hi,

I have 4 Biztalk Servers and 2 separate SQL Server clusters.

I plan to have 1 group for the 4 Biztalk servers. Should I have the MessageBoxDB in SQL Cluster 1 and the rest of the biztalk databases on SQL Cluster 2. Please advice.

Regards,

Sharmishtha

September 7th, 2015 2:34am

Do you have BOTH the SQL Nodes licensed?

I have found that it is easier to group BizTalk databases into the following Resource Groups (each resource Group is a separate Named Instance).

  1. BizTalk Management Resource Group - covers BizTalkMgmtDb and BizTalkRulesEngineDb
  2. BizTalk SSO Resource Group - only BizTalkSSODb
  3. BizTalk Message Box Resource Group - only BizTalkMessageDb
  4. BizTalk Archiving Resource Group - only BizTalkDTADb
  5. BizTalk Analysis Group - special because SQL Analysis Services needs to be installed into this resource group and covers all the BAM related database from BAMAlertsApplication to BAMAlertsNSMail to BAMPrimaryImport to BAMArchiveDb to BAMStarSchema.
  6. BizTalk Applications Group - host other databases such as EDI, A4SWIFT, etc. in this group.

To get maximum benfits, license both your SQL Servers and distribute these resource groups across the two servers. Configure one MSDTC per resource Group. Use tmMappingSet to assign the resource groups to clustered MSDTC.

The reasons are available in the BizTalk Operations Guide. DTA is a high r/w while BAM requires different access. MessageBox has high R/W while Management is Read Optimized.... so if you club this will appropriate SAN storage you would created an environment more tuned towards performance.

Regards.

Free Windows Admin Tool Kit Click here and download it now
September 7th, 2015 2:53am

Do you have BOTH the SQL Nodes licensed?

I have found that it is easier to group BizTalk databases into the following Resource Groups (each resource Group is a separate Named Instance).

  1. BizTalk Management Resource Group - covers BizTalkMgmtDb and BizTalkRulesEngineDb
  2. BizTalk SSO Resource Group - only BizTalkSSODb
  3. BizTalk Message Box Resource Group - only BizTalkMessageDb
  4. BizTalk Archiving Resource Group - only BizTalkDTADb
  5. BizTalk Analysis Group - special because SQL Analysis Services needs to be installed into this resource group and covers all the BAM related database from BAMAlertsApplication to BAMAlertsNSMail to BAMPrimaryImport to BAMArchiveDb to BAMStarSchema.
  6. BizTalk Applications Group - host other databases such as EDI, A4SWIFT, etc. in this group.

To get maximum benfits, license both your SQL Servers and distribute these resource groups across the two servers. Configure one MSDTC per resource Group. Use tmMappingSet to assign the resource groups to clustered MSDTC.

The reasons are available in the BizTalk Operations Guide. DTA is a high r/w while BAM requires different access. MessageBox has high R/W while Management is Read Optimized.... so if you club this will appropriate SAN storage you would created an environment more tuned towards performance.

Regards.

  • Marked as answer by Sharmishtha 18 hours 42 minutes ago
September 7th, 2015 6:52am

Do you have BOTH the SQL Nodes licensed?

I have found that it is easier to group BizTalk databases into the following Resource Groups (each resource Group is a separate Named Instance).

  1. BizTalk Management Resource Group - covers BizTalkMgmtDb and BizTalkRulesEngineDb
  2. BizTalk SSO Resource Group - only BizTalkSSODb
  3. BizTalk Message Box Resource Group - only BizTalkMessageDb
  4. BizTalk Archiving Resource Group - only BizTalkDTADb
  5. BizTalk Analysis Group - special because SQL Analysis Services needs to be installed into this resource group and covers all the BAM related database from BAMAlertsApplication to BAMAlertsNSMail to BAMPrimaryImport to BAMArchiveDb to BAMStarSchema.
  6. BizTalk Applications Group - host other databases such as EDI, A4SWIFT, etc. in this group.

To get maximum benfits, license both your SQL Servers and distribute these resource groups across the two servers. Configure one MSDTC per resource Group. Use tmMappingSet to assign the resource groups to clustered MSDTC.

The reasons are available in the BizTalk Operations Guide. DTA is a high r/w while BAM requires different access. MessageBox has high R/W while Management is Read Optimized.... so if you club this will appropriate SAN storage you would created an environment more tuned towards performance.

Regards.

  • Marked as answer by Sharmishtha Monday, September 07, 2015 12:18 PM
Free Windows Admin Tool Kit Click here and download it now
September 7th, 2015 6:52am

Do you have BOTH the SQL Nodes licensed?

I have found that it is easier to group BizTalk databases into the following Resource Groups (each resource Group is a separate Named Instance).

  1. BizTalk Management Resource Group - covers BizTalkMgmtDb and BizTalkRulesEngineDb
  2. BizTalk SSO Resource Group - only BizTalkSSODb
  3. BizTalk Message Box Resource Group - only BizTalkMessageDb
  4. BizTalk Archiving Resource Group - only BizTalkDTADb
  5. BizTalk Analysis Group - special because SQL Analysis Services needs to be installed into this resource group and covers all the BAM related database from BAMAlertsApplication to BAMAlertsNSMail to BAMPrimaryImport to BAMArchiveDb to BAMStarSchema.
  6. BizTalk Applications Group - host other databases such as EDI, A4SWIFT, etc. in this group.

To get maximum benfits, license both your SQL Servers and distribute these resource groups across the two servers. Configure one MSDTC per resource Group. Use tmMappingSet to assign the resource groups to clustered MSDTC.

The reasons are available in the BizTalk Operations Guide. DTA is a high r/w while BAM requires different access. MessageBox has high R/W while Management is Read Optimized.... so if you club this will appropriate SAN storage you would created an environment more tuned towards performance.

Regards.

  • Marked as answer by Sharmishtha Monday, September 07, 2015 12:18 PM
September 7th, 2015 6:52am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics