none
BizTalkMsgBoxDb.dbo.bts_DeQueueMessages_ProcessHost is causing lock in the biztalk instance and message was processing really slow RRS feed

  • Question

  • hi all, we've used msft performance dashboard reports and locate this culprit. however , seems it is recurring issue,

    is there anything we could do to fix it for good? 

    the culprit is BizTalkMsgBoxDb.dbo.bts_DeQueueMessages_ProcessHost

    thanks

    Hui


    --Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

    Thursday, June 7, 2018 6:27 AM

All replies

  • Hi,

    it looks there are numbers of Orphan message lying into the BizTalk MessageBox DB, which in turn becomes zombie and used nowhere. you can safely identify and remove these zombie messages(Link#1).

    1) lookout for HOSTQ table (i.e. [BizTalkMsgBoxDb].[dbo].[BizTalkServerApplicationQ]) and look for records whose dtValid greater than 2 months

    2) use BizTalk Health Monitor (Link#2) and delete the Orphan messages safely from BizTalk Message Box database.



    please refer the below article focus more issue similar to you.

    Link#1 http://www.sqlserverfaq.net/2010/05/29/high-cpu-on-sql-server-running-biztalk-instances-2/

    Link#2 https://www.microsoft.com/en-in/download/details.aspx?id=43716


    Hope this Helps!!!!!

    (Please Mark as Answered if you satisfy with Reply)
    Thursday, June 7, 2018 1:32 PM
  • thanks Vikas. Can you tell me what this SP does? 

    bts_DeQueueMessages_ProcessHost 

    it seems the link#1 is about 

    BTS_DEQUEUEMESSAGES_BIZTALKSERVERISOLATEDHOST

    not quite the same.

    Thanks

    Hui


    --Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

    Thursday, June 7, 2018 1:53 PM
  • Which BTS version?
    If you are using Visual Studio 2003 it could be as old as BTS 2004?

    Not sure if BizTalk Health Monitor (BHM) supports this version otherwise you need at least an elder version of the terminator tool can be difficult to find

    General rules
    1) Make sure all Biztalk SQL Agent jobs are configured and runnning in schedule correctly (SQL Server agent -> History)
    2) Make sure you do not have a large amount of suspended message (BTS Admin -> Group Hub)
    3) Make sure you do not have a large amount of dehydrated messages ( --do -- )

    If you have BTS 2010 or 2013 the BHM is a good option for monitoring and get to know the performance of your installation 
    https://www.microsoft.com/en-us/download/details.aspx?id=43716

    Overview
    https://blogs.msdn.microsoft.com/biztalkhealthmonitor/2014/06/26/overview-of-biztalk-health-monitor-bhm/
    From BTS 2013R2 the BHM is included with the installation

    hth/Peter

    Thursday, June 7, 2018 2:35 PM