Filed under: Biztalk 2004, Monitoring Biztalk | Tags: BizTalk, Biztalk Server 2004, HAT, Heath and Activity Tracking, Monitor, Tracking
If you like to clean up the tracking database of Biztalk Server 2004, you can just do this by running some little queries.
Open Query Analyzer and connect to the (Biztalk Tracking) BizTalkDTADb database. Then open the file called Purge_DTADB.sql in the next directory: “C:\Program Files\Microsoft BizTalk Server 2004\SDK\Samples\Admin\Database Maintenance”. Run this script (F5) and this script will create a storedprocedure called ‘dtasp_PruneTrackingDatabase’. This sp takes only a single parameter called: @PruneBeforeDate. Executing this SP causes the tracking data to be purged that was older then the given date (more…)
Filed under: Biztalk 2004, Covast EDI Accelerator, Problems | Tags: Accelerator, BizTalk, Biztalk Server 2004, Covast, CovastDB, EDI, repolock, repository
When you want to deploy the Covast Engine Input File (EIF) and you receive an error about an locked EDI repository, please read on for the solution. Covast locks his repository in the table called ‘parame’. So here lies also the possibility to ‘unlock’ your repository! (more…)
Filed under: Biztalk 2004, Biztalk Errors, Covast EDI Accelerator | Tags: Accelerator, BizTalk, Biztalk Server 2004, Covast, document definitions, EDI, Schema
When you like to change the maxlength parameter of an numeric element of an EDI message, you’ll find out that there is a dirty, nasty little bug in Covast. It can take you weeks to find out how this is actually working.
So as an example, we’re going to change and fix (max) length value of the 9308 Seal_Number element located in the EDI ‘IFTMIN D 99B Default UN’ message. First we open Covast Studio and go to the document repository. (more…)
