Dear All,

I have a question regarding the suspended messages. In fact in our
integration server we have suspended messages dating from the begining
2004 (begining of the project). These suspended messages info are
useless especially now (we have more than 400 000 suspended messages).

Is there a way to kill all these messages and get rid of them in the
Database at once? Using the HAT is fastidious and not very practicle
especially in deleting all the 400 000 suspended messages.

My last desperate action would be to truncate the following tables in
the BizTalkMsgBoxDb, is it recomanded? is there a MS Script that does
this?

BizTalkServerApplicationQ_Suspended
Instaces
messageparts
messagerefcountlogtotals
partrefcountlogtotals
parts
spool

Any help would be greatly appreciated...

Thanks,
Stefan

[ Post a follow-up to this message ]

Hello Stefan,

Manipulating the BTS database directly is not a recommended way but I think
you don't have much other options

My suggestion would be to start the SQL profiler and see what happens in
the database when you terminate one instance or a couple of instances using
HAT.
After that take the query from SQL profiler and modify/extend it so it can
be used to terminate all messages.

Please, post the query if you have this working ;-)

HTH,

Randal van Splunteren
http://biztalkia.blogspot.com

> Dear All,
>
> I have a question regarding the suspended messages. In fact in our
> integration server we have suspended messages dating from the begining
> 2004 (begining of the project). These suspended messages info are
> useless especially now (we have more than 400 000 suspended messages).
>
> Is there a way to kill all these messages and get rid of them in the
> Database at once? Using the HAT is fastidious and not very practicle
> especially in deleting all the 400 000 suspended messages.
>
> My last desperate action would be to truncate the following tables in
> the BizTalkMsgBoxDb, is it recomanded? is there a MS Script that does
> this?
>
> BizTalkServerApplicationQ_Suspended
> Instaces
> messageparts
> messagerefcountlogtotals
> partrefcountlogtotals
> parts
> spool
> Any help would be greatly appreciated...
>
> Thanks,
> Stefan

[ Post a follow-up to this message ]

Hello Stefan,

You can also have a look at this post:

http://blogs.msdn.com/biztalk_core_.../09/390996.aspx

HTH,
Randal van Splunteren
http://biztalkia.blogspot.com

> Dear All,
>
> I have a question regarding the suspended messages. In fact in our
> integration server we have suspended messages dating from the begining
> 2004 (begining of the project). These suspended messages info are
> useless especially now (we have more than 400 000 suspended messages).
>
> Is there a way to kill all these messages and get rid of them in the
> Database at once? Using the HAT is fastidious and not very practicle
> especially in deleting all the 400 000 suspended messages.
>
> My last desperate action would be to truncate the following tables in
> the BizTalkMsgBoxDb, is it recomanded? is there a MS Script that does
> this?
>
> BizTalkServerApplicationQ_Suspended
> Instaces
> messageparts
> messagerefcountlogtotals
> partrefcountlogtotals
> parts
> spool
> Any help would be greatly appreciated...
>
> Thanks,
> Stefan

[ Post a follow-up to this message ]

By looking at the profiler many stored procedures are called and every
procedure needs guids corresponding to different instaceIDs MessageIDs,
... etc.

So I did what I had to do... I truncated the tables described above and
everything seems to work fine.

But this is still a question for Microsoft. How can we terminate
suspended messages and suspended orchestrations after let's say 1
month?? If we do nothing all the messages will be suspended for ever
!!! the database would get bigger, and the performances and BizTalk
functionning would be greatly altered. For this problem, our company
and our client were working on it for a couple of days.... SO ou
Microsoft friends please do something...

Thanks
Stefan

[ Post a follow-up to this message ]

You can also use WMI to terminate the suspended messages.  There's an
example here :

http://dallas.sark.com/SarkBlog/mho...ticles/337.aspx

Stefan wrote:
> By looking at the profiler many stored procedures are called and every
> procedure needs guids corresponding to different instaceIDs MessageIDs,
> ... etc.
>
> So I did what I had to do... I truncated the tables described above and
> everything seems to work fine.
>
> But this is still a question for Microsoft. How can we terminate
> suspended messages and suspended orchestrations after let's say 1
> month?? If we do nothing all the messages will be suspended for ever
> !!! the database would get bigger, and the performances and BizTalk
> functionning would be greatly altered. For this problem, our company
> and our client were working on it for a couple of days.... SO ou
> Microsoft friends please do something...
>
> Thanks
> Stefan
>

[ Post a follow-up to this message ]

Yes, exec bts_CleanupMsgbox can work just fine.  Have a look here, though,
too -
http://www.traceofthought.net/Perma...1c.
aspx

Scott Colestock
www.traceofthought.net

"Randal van Splunteren" <randal.van.splunteren@hotmail.com> wrote in message
news:3ee20e0fdecb8c82dee489af1f0@news.microsoft.com...
> Hello Stefan,
>
> You can also have a look at this post:
>
> http://blogs.msdn.com/biztalk_core_.../09/390996.aspx
>
> HTH,
> Randal van Splunteren
> http://biztalkia.blogspot.com
> 
>
>

[ Post a follow-up to this message ]