Click to Rate and Give Feedback
MSDN
MSDN Library
BizTalk Server
Operations
 How to Manually Purge Data from the...
Collapse All/Expand All Collapse All
How to Manually Purge Data from the BizTalk Tracking Database

The DTA Archive and Purge SQL Server Agent job reduces the need to manually purge data from the BizTalk Tracking (BizTalkDTADb) database due to continuous purging of the database and compaction of stored tracking data. You might need to manually purge data if your BizTalk Tracking (BizTalkDTADb) database has grown so much that sustained performance degradation is occurring and the DTA Archive and Purge job is unable to keep up with the database growth.

Aa561918.Caution(en-us,BTS.20).gifCaution
Performing this procedure deletes all tracking data for completed instances from the BizTalk Tracking (BizTalkDTADb) database regardless of completion time. Before performing this procedure, you should archive the BizTalk Tracking (BizTalkDTADb) database separately from the other BizTalk Server databases.

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. Backup your BizTalk Server databases.

  2. Archive the BizTalk Tracking (BizTalkDTADb) database.

  3. Open Services. Click Start, click Run, and then type services.msc.

  4. Right-click each of the following services, and then click Stop:

    • BizTalk Base EDI Service

    • Enterprise Single Sign-On Service

    • Rule Engine Update Service

  5. Click Start, click Programs, click Microsoft BizTalk Server 2006, and then click BizTalk Server Administration.

  6. In the BizTalk Server Administration Console, double-click the BizTalk Group, double-click Platform Settings, and then double-click Host Instances.

  7. In the details pane, right-click each running host instance, and then click Stop.

  8. Click Start, click Run, type cmd, and then click OK.

  9. At the command prompt, type:

    net stop iisadmin /y

    This stops the IIS Admin Service and all dependent services, one-by-one and prevents new data from being written to the BizTalkDTADb while data is being purged. Write down the list of services as each one is stopped. You will need to use this list of services later when you restart IIS.

    Below is an example of the output you will see after issuing this command (the dependent services listed on your computer may vary):

    The following services are dependent on the IIS Admin Service service. Stopping the IIS Admin Service service will also stop these services.
    World Wide Web Publishing Service
    HTTP SSL
  10. Click Start, click Programs, click Microsoft SQL Server 2005, and then click SQL Server Management Studio.

  11. In the Connect to Server dialog box, specify the name of the SQL server where the BizTalk Tracking (BizTalkDTADb) database resides and the appropriate authentication type, and then click Connect to connect to the appropriate SQL server.

  12. In Microsoft SQL Server Management Studio, double-click Databases, double-click the BizTalkDTADb database, double-click Programmability, and then click Stored Procedures.

  13. In the details pane, right-click dtasp_PurgeAllCompletedTrackingData, and then click Execute Stored Procedure.

  14. In the Execute Procedure dialog box, click OK.

    This stored procedure deletes all tracking data associated with completed instances regardless of their completion time.

  15. Open Services. Click Start, click Run, and then type services.msc.

  16. Right-click each of the following services, and then click Start:

    • BizTalk Base EDI Service

    • Enterprise Single Sign-On Service

    • Rule Engine Update Service

  17. Click Start, click Programs, click Microsoft BizTalk Server 2006, and then click BizTalk Server Administration.

  18. In the BizTalk Server Administration Console, double-click the BizTalk Group, double-click Platform Settings, and then double-click Host Instances.

  19. In the details pane, right-click each stopped host instance, and then click Start.

  20. Click Start, click Run, type cmd, and then click OK.

  21. At the command prompt, restart each of the IIS services that you stopped in step 6. Type:

    net start <IISserviceName>

    Where <IISserviceName> is the name of the IIS service you want to restart. You must repeat this command for each of the IIS services.

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Processing
© 2009 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement | Site Feedback
Page view tracker