BizTalk 2009 RTM Upgrade Gotchas – Tracking Data

Originally posted by Nick Heppleston at: http://www.modhul.com/2009/04/11/biztalk-2009-rtm-upgrade-gotchas-tracking-data/

I’ve started to play around with my new BizTalk 2009 installation following my upgrade fromBizTalk 2006 R2 and I’ve noticed a few quirks that you may need to watch out for, following an upgrade.

Tracking Data

The new Admin Console comes with a bunch of new queries relating to your tracking data, including the ability to view Tracked Service Instances and Message Events:

bts-admin-console-tracked-message-counts

Drilling into the Tracked Message Events view presents the usual Query Results, displaying tracked message events from the BizTalkDTADb dta_MessageInOutEvents and dta_ServiceInstances tables among others:

bts-admin-console-tracked-message-events-results

However, drilling further into an individual message presents the following error dialog:

bts-admin-console-tracked-message-counts-error-dialog

The message was not found in the Message Box or the Tracking databases. This may be caused by one of the following conditions: (1) message tracking is not enabled; (2) the message(s) is no longer referenced by a running or suspended service instance; (3) the Message Box tracking tables have been automatically purged; or (4) the SQL Server agent is not running on the Message Box servers. (Microsoft.BizTalk.Administration.SnapIn)

It would appear that when the upgrade ‘upgrades’ the tracking databases, some have their data truncated (possibly to allowing the structure of the table to be changed) while others are left untouched. In the above case, tracked data written to the dta_MessageInOutEvents and dta_ServiceInstances tables remains untouched, while data written to the tracking_spool1 and tracking_spool2 tables is truncated (double-clicking a query result item causes the BizTalk Admin Console to issue a call to the ops_LoadTrackedMessages stored procedure, passing in the GUID of the MessageId in question; the stored proc in turn queries the two tracking spool tables and no data is returned).

Takeaway

Don’t rely on your tracking data being available after an upgrade to BizTalk 2009; take a backup of the data before you begin the upgrade and query that data in an offline mode.

Reblog this post [with Zemanta]
Advertisements

3 thoughts on “BizTalk 2009 RTM Upgrade Gotchas – Tracking Data

  1. Good find on this, frustrating to lose data from any aspect, but better to know before hand to prepare for the possible disaster than finding out after the fact.

  2. Hi Nick,

    Just wondered if you had any problems migrating BTS06 R2 Applications to BTS09 using the migration wizard in VS2008. My general experience is that it fails to convert any BizTalk project files with the following error

    Error converting project file. Child element of element is not valid.

    which I beleive was an error in the beta version, has this not been fixed?

    • Hey Jim,
      I haven’t tried the migration wizard – I simply deployed an existing BTS2006 solution to BTS2009 and it worked. I will try and recreate your problem with the migration wizard. Watch this space!

      Nick.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s