I have a single business process running in production.  It takes incoming
messages (from a database), processes and translates them and sends the
message contents out.  The incoming messages usually contain several
records that each get sent back out to their final destination (a different
database).

The process appears to run flawlessly, but it produces a ton of tracking
data.  I have setup the BizTalk SDK stored procedure that purges data from
the tracking database and configured it to run each night, keeping only 7
days worth of data.  However, each day we add about 1G of tacking data.
Why?  What is in there?

HAT is timing out when I try to get a count of messages for a day.  Is
there some other way for me to do this?

What will happen if I just turn off tracking for the host the process is
running in?

What is going to happen when the next three processes go in to production?


--
Jake Watkins
jakew - guerillaprogrammer.com
MCSD - .NET, Web-services, BizTalk, BPM
469-855-5919

[ Post a follow-up to this message ]