Move the BAM Notification Services Databases
You can use this procedure to move the BAM Notification Services databases to another server.
Note
You must move the BAM Notification Services Application (BAMAlertsApplication) database and BAM Notification Services Instance (BAMAlertsNSMain) database together.
Prerequisites
You must be logged on with an account that is a member of the SQL Server sysadmin fixed server role to perform this procedure.
To move the BAM Notification Services databases
Get a copy of the .xml file used for restoring BAM:
Click Start, click Run, type cmd, and then click OK.
At the command prompt, navigate to the following directory:
%SystemDrive%\Program Files\Microsoft BizTalk Server \Tracking
At the command prompt, type:
Bm.exe get-config –filename:BAMConfiguration.xml
Note
On a system that supports User Account Control (UAC), you may need to run the tool with Administrative privileges.
At the command prompt, type:
Net stop NS$BamAlerts
Follow the instructions in SQL Server Books Online on how to back up the database on the old server.
Copy the BAM Notification Services databases to the new SQL server.
Follow the instructions in SQL Server Books Online on how to restore the database on the new server.
Edit the BAMConfiguration.xml file and change the ServerName in the Alert DeploymentUnit section to the new server name.
Save and close the BAMConfiguration.xml file.
Click Start, click Run, type cmd, and then click OK.
At the command prompt, navigate to the following directory:
%SystemDrive%\Program Files\Microsoft BizTalk Server \Tracking
At the command prompt, type:
bm.exe update-config -FileName:BAMConfiguration.xml
Note
On a system that supports User Account Control (UAC), you may need to run the tool with Administrative privileges.
Update references to the BAM Notification Services databases. For more information, see How to Update References to the BAM Notification Services Databases.