You configure the BAMArchive database for a Microsoft BizTalk Server 2010 group to use a custom filegroup as the default filegroup.
You deploy a Business Activity Monitoring (BAM) activity.
Note In this case, an instances table (bam_<activity_name>_Instances) that uses the default filegroup is created in the BAMArchive database.Additionally, some BAM data is generated for the deployed activity in the BAMPrimaryImport database.
You run the BAM_DM_<activity_name> Microsoft SQL Server Integration Services (SSIS) package to archive the generated data from the BAMPrimaryImport database to the BAMArchive database.
In this scenario, the bam_<activity_name>_Instances table in the BAMArchive database is changed to use the primary filegroup unexpectedly.
This issue occurs because the generated BAM SSIS package for the BAM activity changes the instances table to use the primary filegroup.
After you apply this cumulative update package, the generated BAM SSIS package for the deployed BAM activity changes the instances table to use the default filegroup instead of the primary filegroup.
Cumulative update information
For BizTalk Server 2010
The fix that resolves this issue is included in cumulative update package 5 for BizTalk Server 2010.
For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2689458 Cumulative update package 5 for BizTalk Server 2010
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to manage BAM database, go to the following MSDN website: