You must be logged on with an account that is a member of the SQL Server sysadmin fixed server role to perform this procedure.

1. Stop all BizTalk Server services. For more information, see How to Start, Stop, Pause, Resume, or Restart BizTalk Server Services.

   Important
   It is critical to make sure that all the BizTalk Server services and jobs are stopped before you move the databases.

2. Stop the IIS service.

3. Stop the SQL Server Agent service.

4. Back up the BizTalk databases by following the database backup procedures as described at http://go.microsoft.com/fwlink/?LinkId=138178.

5. Restore the BizTalk databases on the new server following the database restore procedures at http://go.microsoft.com/fwlink/?LinkId=138179.

6. Script the SQL Server Agent jobs listed below for transfer to the new server.

   Run each of the scripts on the new server to recreate the jobs. Certain jobs, such as the Backup BizTalk Server (BizTalkMsgBoxDb) job, will have to be reconfigured unless the new server file paths and server name are identical to the old server.

   Note
   You can also use the SSIS/DTS Transfer Jobs task to move the jobs to the new server, but most users will probably find it easier to script the jobs using SQL Management Studio.

   • Backup BizTalk Server (BizTalkMgmtDb)
     
     
   • CleanupBTFExpiredEntriesJob_BizTalkMgmtDb
     
     
   • DTA Purge and Archive (BizTalkDTADb)
     
     
   • MessageBox_DeadProcesses_Cleanup_BizTalkMsgBoxDb
     
     
   • MessageBox_Message_Cleanup_BizTalkMsgBoxDb
     
     
   • MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb
     
     
   • MessageBox_Parts_Cleanup_BizTalkMsgBoxDb
     
     
   • MessageBox_UpdateStats_BizTalkMsgBoxDb
     
     
   • Operations_OperateOnInstances_OnMaster_BizTalkMsgBoxDb
     
     
   • PurgeSubscriptionsJob_BizTalkMsgBoxDb
     
     
   • Rules_Database_Cleanup_BizTalkRuleEngineDb
     
     
   • TrackedMessages_Copy_BizTalkMsgBoxDb
     
     

7. In addition to scripting SQL Server Agent jobs as described in the previous step, you must also script logins and restore them on the new server. The following logins should be scripted, along with any custom logins you have created:

   • BizTalk Application Users
     
     
   • BizTalk Isolated Host Users
     
     
   • BizTalk Server Administrators
     
     
   • BizTalk Server Operators
     
     
   • SSO Administrators
     
     SSO Administrators is needed only if you also intend to move the SSODB.
     
     

8. Restore the BizTalk Server databases by following steps 6 through 12 in How to Restore Your Databases. This procedure updates the BizTalk Management (BizTalkMgmtDb) database and registry with the new location of the BizTalk databases.

   Note
   In the SampleUpdateInfo.xml file, comment out all of the databases except for those you have moved to the new server.

Concepts