Microsoft KB Archive/832725

= How to move BizTalk Server 2002 databases from one computer that is running SQL Server to another =

Article ID: 832725

Article Last Modified on 8/6/2004

-

APPLIES TO


 * Microsoft BizTalk Server 2002 Standard Edition

-



SUMMARY
This article describes how to move your Microsoft BizTalk Server 2002 databases from one computer that is running Microsoft SQL Server to another computer that is running SQL Server.



MORE INFORMATION
 On the computer that is running BizTalk Server:  In Control Panel, double-click Services. In Services, right-click BizTalk Messaging Service, and then click Stop to stop the Microsoft BizTalk Messaging Service.  On the source computer that is running SQL Server, right-click Start, and then click Explore to start Microsoft Windows Explorer. Locate the Program Files\Microsoft SQL Server\MSSQL\Data folder or the folder where the SQL Server data files are located. On the source computer, start another instance of Windows Explorer, and then locate the Program Files\Microsoft SQL Server\MSSQL\Data folder or the folder where the SQL Server data files are located on the destination computer that is running SQL Server. In SQL Enterprise Manager on the source computer, stop SQL Server:  Click Start, point to Programs, point to Microsoft SQL Server, and then click Enterprise Manager.</li> In Enterprise Manager, locate the source computer.</li> Right-click the source computer, and then click Stop.</li></ol> </li> On the source computer, copy the following files that are located in the folder where your SQL Server data files are located, and then paste these files in the folder where your SQL Server data files are located on the destination computer.

Note These database names assume that you used the default names for the BizTalk Server databases during BizTalk Server setup. <ul> InterchangeBTM.mdf</li> InterchangeBTM_log.ldf</li> InterchangeDTA_Data.mdf</li> InterchangeDTA_Log.ldf</li> InterchangeSQ_Data.mdf</li> InterchangeSQ_Log.ldf</li> XLANG_Data.mdf</li> XLANG_Log.ldf</li></ul> </li> Register the destination computer in a SQL Server group in SQL Server Enterprise Manager so that you can remotely administer the destination computer.</li> In SQL Server Enterprise Manager, connect to the destination computer that is running SQL Server.</li> Right-click Databases, click All Tasks, and then click Attach Database.</li> <li>Locate the InterchangeBTM.mdf file (or the data file that contains your Messaging Management objects) that you copied to the destination computer in step 5, and then click OK.</li> <li>In the Attach Database dialog box, change the database owner name that appears in the Specify database owner drop-down list box to the appropriate account name, and then click OK. Click OK again.</li> <li>Repeat steps 8 through 10 for the InterchangeDTA_Data.mdf file, for the InterchangeSQ_Data.mdf file, and for the XLANG_Data.mdf file (or for the data files that contain your Tracking, Shared Queue, and XLANG databases) to create the InterchangeDTA database, the InterchangeSQ database, and the XLANG database.</li> <li>Start BizTalk Server Administrator, right-click the root node of the displayed hierarchy, and then click Properties. The displayed hierarchy should be either &quot;Microsoft BizTalk Server 2000&quot; or &quot;Microsoft BizTalk Server 2002.&quot;</li> <li>In the SQL Server name text box, type the name of the destination computer, and then click OK.</li> <li>Right-click the BizTalk Server group where your computer that is running BizTalk Server is located, and then click Properties.</li> <li>In the Properties dialog box, click the Connection tab. In Tracking SQL Server name and Shared Queue SQL Server name, type the name of the destination computer, and then click OK.</li> <li>Right-click the first server in the group again, and then click Start.

Note Make sure that the BizTalk Messaging Service is configured to run under the context of an account that has database owner (dbo) permissions on the BizTalk databases that you have created on the destination computer.</li> <li>Repeat steps 14 through 16 for any servers in the BizTalk Server group that you want to change the location of the Tracking and Shared queue databases for.</li> <li>Click Start, point to Programs, point to Administrative Tools, and then click Component Services. In the Component Services management interface, locate the XLANG Scheduler COM+ application.</li> <li>Right-click XLANG Scheduler, and then click Shut down.</li> <li>Right-click XLANG Scheduler, and then click Properties. In the Properties dialog box, click the XLANG tab.</li> <li>Click Configure DSN to start the ODBC Data Source Administrator. In the ODBC Data Source Administrator, click the File DSN tab.</li> <li>Double-click the XLANG Scheduler.dsn data source to start the DSN configuration wizard.</li> <li>In the Which SQL Server do you want to connect to? text box, type the name of the destination computer, and then click Finish.</li> <li>Click Test Data Source to verify connectivity, and then click OK four times to close Data Source Test, the DSN configuration Wizard, the ODBC Data Source Administrator, and the XLANG Scheduler COM+ application Properties dialog box.</li> <li>Update the Connection.vbs file that is located in the \Program Files\Microsoft BizTalk Server\BizTalkTracking\VBScripts\ directory of your BizTalk Server to reference the tracking database on the destination SQL Server so that the BizTalk tracking interface will access the new tracking database. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> <li> Open Connection.vbs in Notepad, and then locate the following parameters: Initial Catalog=InterchangeDTA;Data Source=SQLSERVER </li> <li>Modify these parameters to point to the new tracking database.</li></ol> </li></ol>

Keywords: kbhowto KB832725

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.