The BizTlkDTADb and BizTalkMsgBoxDb databases are getting quite large,
23388.31 MB and 7969.13 MB resepctively.  I imagine its because messages
just keep getting archived in the databases and never get removed, is that
correct?  If so are there jobs or scripts we can run to remove old messages
that aren't required anymore?

[ Post a follow-up to this message ]

If the message box continues to grow, it indicates a problem you need to
address (messages are getting suspended, or you aren't keeping up with
incoming work, etc.)

The tracking database requires a specific archive and purge strategy -
sample scripts are available in the SDK for 2004 (and installed by default
in 2006, though the job is not enabled.)  (As an alternative, you can
disable tracking if you aren't going to utilize it.)

Scott Colestock
www.traceofthought.net


"Jeremy Chapman" <please@Idontlikespam> wrote in message
news:eWJx6VYiGHA.2456@TK2MSFTNGP04.phx.gbl...
> The BizTlkDTADb and BizTalkMsgBoxDb databases are getting quite large,
> 23388.31 MB and 7969.13 MB resepctively.  I imagine its because messages
> just keep getting archived in the databases and never get removed, is that
> correct?  If so are there jobs or scripts we can run to remove old
> messages that aren't required anymore?
>

[ Post a follow-up to this message ]

We get an error when we try to run this script (even at 2am when usage is
very low):

Server: Msg 1204, Level 19, State 1, Procedure dtasp_PruneTrackingDatabase,
Line 26
The SQL Server cannot obtain a LOCK resource at this time. Rerun your
statement when there are fewer active users or ask the system administrator
to check the SQL Server lock and memory configuration.


Do I need to stop the BizTalk service, do the purge, then Restart it?  I'm
not really fond of duing that.



"Scott Colestock" <scolestock@community.nospam> wrote in message
news:%23bUAmOZiGHA.3320@TK2MSFTNGP03.phx.gbl...
>
> If the message box continues to grow, it indicates a problem you need to
> address (messages are getting suspended, or you aren't keeping up with
> incoming work, etc.)
>
> The tracking database requires a specific archive and purge strategy -
> sample scripts are available in the SDK for 2004 (and installed by default
> in 2006, though the job is not enabled.)  (As an alternative, you can
> disable tracking if you aren't going to utilize it.)
>
> Scott Colestock
> www.traceofthought.net
>
>
> "Jeremy Chapman" <please@Idontlikespam> wrote in message
> news:eWJx6VYiGHA.2456@TK2MSFTNGP04.phx.gbl... 
>
>

[ Post a follow-up to this message ]