November 14, 2018 at 2:00 pm
I have a general ? for a generalized problem. Have a biztalk 2013 that communicates to our sql 2016 server. It constantly seems to have blocking and deadlock issues and what I can trap is not the most useful.. I dont control the biztalk code just have to live with the problems with these distributed transactions. From anyone out there who has this dilemma have you found any best practices in dealing with this? Thanks
November 14, 2018 at 2:15 pm
tcronin 95651 - Wednesday, November 14, 2018 2:00 PMI have a general ? for a generalized problem. Have a biztalk 2013 that communicates to our sql 2016 server. It constantly seems to have blocking and deadlock issues and what I can trap is not the most useful.. I dont control the biztalk code just have to live with the problems with these distributed transactions. From anyone out there who has this dilemma have you found any best practices in dealing with this? Thanks
The following article has some decent general guidelines (used to be a KB article):
Checklist: Maintaining and Troubleshooting BizTalk Server Databases
The locking and blocking issues is just how BizTalk works. Deadlocks shouldn't be much of an issue if you follow some of the tips in the above article and consider increasing the frequency of the log backups. You're in a painful situation - follow those practices in the article (and the link to best practices in that checklist) and what I usually ended up doing is paying attention mostly to the jobs, disk performance and those guideliness. If it has the resources it needs and you follow all the guidelines that's usually the best you can do.
Sue
November 14, 2018 at 2:25 pm
should have clarified, the deadlocks and blocking I get are on the OLTP database Biztalk communicates with not the BizTalk native databases
November 14, 2018 at 2:44 pm
tcronin 95651 - Wednesday, November 14, 2018 2:25 PMshould have clarified, the deadlocks and blocking I get are on the OLTP database Biztalk communicates with not the BizTalk native databases
I only know of the BizTalkMsgBoxDB as the OLTP database for BizTalk. BizTalk service handles the deadlocks for that database. If you are integrating with something else, I have no idea. All the checklists and the best practices link still apply. Personally, I would look at them and implement the suggestions.
Sue
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply