This service pack includes the following features:

• Automated Archiving and Purging of the BizTalk Tracking Database
  
  As BizTalk Server processes more and more data on your system, the BizTalk Tracking (BizTalkDTADb) database continues to grow in size. Unchecked growth decreases system performance and may generate errors in the Tracking Data Delivery Service (TDDS). In addition to general tracking data, tracked messages can also accumulate in the MessageBox database, causing poor disk performance.
  
  While BizTalk Server 2004 included sample scripts for archiving tracked messages and purging the BizTalk Tracking database, archiving and purging in BizTalk Server 2004 SP2 automates both processes using the DTA Purge and Archive job. By archiving and purging data from the BizTalk Tracking database, you can maintain a healthy system, as well as keep your tracking data archived for future use. Because BizTalk Tracking database archives accumulate over time and consume disk space, it is a good idea to move the BizTalk Tracking database archives to secondary storage on a regular basis.
  
  For more information about Archiving and Purging the BizTalk Tracking Database in BizTalk Server 2004 SP2, see http://go.microsoft.com/fwlink/?LinkID=69104.
  
  

This service pack has the following known issues:

• Issue: Backing up your BizTalk Server databases before installing SP2
  
  Uninstalling BizTalk Server 2004 SP2 uninstalls the SP2 binaries and restores the BizTalk Server binaries to their SP1 state. SP2 contains major database schema changes and uninstalling SP2 does not restore BizTalk Server databases to their SP1 state.
  
  After uninstalling SP2, you must restore the BizTalk Server databases from your backup. You must back up your BizTalk Server databases to ensure you can recover from a failure during the SP2 installation process.
  
  
• Issue: Restoring the BizTalk Server databases before uninstalling SP1
  
  SP2 changes the database schema. Before uninstalling SP1, you must restore the database schema to its SP1 state. In other words, to uninstall both SP2 and SP1, you must uninstall SP2, restore the BizTalk Server databases to return the schema to the SP1 state, and then uninstall SP1.
  
  
• Issue: Backup Job Does Not Include SSO Database
  
  In order to create a complete backup set, you must add the SSO database (SSODB) to the list of other databases backed up as part of the backup process. To do this, follow the instructions for adding a new backup database to the adm_OtherBackupDatabases table. For more information, see "Backing Up the SSO Credential Database" in the BizTalk Server 2004 Online Help.
  
  In order for the database restore script to find the SSO database, you must set the DefaultDatabaseName for the SSO database entry to SSO.
  
  
• Issue: Using one instance of SQL Server for more than one BizTalk group.
  
  When using one instance of SQL Server for more than one BizTalk group, you must configure the second group after installing SP2 on all of the computers running BizTalk Server in the second group.
  
  
• Issue: You must restart Orchestration Debugger periodically because it does not list out of sequence events.
  
  Orchestration Debugger displays events in order and appends new events to the end of the list. Events that occur out-of-order are not added to the list. To view this event data, you must close and then reopen the Orchestration Debugger.
  
  

Note the following requirements:

• You must install Service Pack 2 (SP2) only on computers already running BizTalk Server 2004 SP1.
  
  
• You must install SP2 on all servers in a farm or group. Mixing SP2 with other versions is not supported.
  
  
• SP2 supports GB18030 (simplified Chinese) characters. Using these characters requires a custom Microsoft SQL Server™ Setup program. For more information, see Knowledge Base article 890602, "Using GB18030 Characters in BizTalk Server 2004, Service Pack 1" at http://go.microsoft.com/fwlink/?LinkID=39417.
  
  
• You must back up your BizTalk Server 2004 databases. For information about backing up your databases, see "Backing Up Your Databases" in Microsoft BizTalk Server 2004 Help.
  
  
• Microsoft Windows® XP Service Pack 2 changes how the system handles remote procedure calls (RPCs). You must make changes to the registry for Enterprise Single Sign-On and other BizTalk Server 2004 services to work. For more information, see Knowledge Base article 841893, "The Enterprise Single Sign-On Service and associated BizTalk Server 2004 services fail after you install Windows XP Service Pack 2 (SP2)" at http://go.microsoft.com/fwlink/?LinkID=39453.
  
  

You do not have to redeploy applications you deployed before installing BizTalk Server 2004 SP2.

You must install BizTalk Server 2004 and BizTalk Server 2004 Service Pack 1 (SP1) before installing Service Pack 2.

The files for Service Pack 2 are in a single executable file, BizTalk 2004 Service Pack 2 <language>.exe, for example, BizTalk 2004 Service Pack 2 ENU.exe. Double-clicking this file unpacks the readme file and an executable file, BTS2004-SP2-<language>.exe, to the directory you indicate in the dialog box. When you open this second executable file, the files are extracted to the current folder, and Setup.exe runs automatically.

If you encounter a problem during installation and no error message appears, review the log file, Setup.log. The default location of the file is %SystemDrive%\Documents and Settings\All Users\Application Data\Microsoft\E-Business Servers Updates\BTS2004\SP2\. A link to this file also appears on the last page of the installation wizard.

Under certain conditions, you may be prompted to restart the computer after installing SP2. This is normal.

Uninstalling BizTalk Server 2004 SP2 uninstalls SP2 binaries and restores BizTalk Server to its SP1 state. Since SP2 contains major database schema changes, uninstalling SP2 does not restore BizTalk Server databases to their SP1 state. You must restore your databases from the backups you made prior to installing SP2.

If you have technical questions about Service Pack 2 not answered in this document or in the Microsoft Knowledge Base articles, Microsoft offers technical support and services.

Product name: Microsoft BizTalk Server 2004 Service Pack 2

Support options: To obtain the latest information about your support options, see the Microsoft Product Support Services Web site at http://go.microsoft.com/fwlink/?LinkId=36792.

Worldwide support: Options, hours, and cost in your country or region may differ from the United States; contact your local office for details.

Conditions: Microsoft Product Support Services are subject to the then-current prices, terms, and conditions at Microsoft, which are subject to change without notice.

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2006 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, and BizTalk are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.