October 7, 2013 at 1:59 pm
I have developers who have build some inserts and extracts from BizTalk into some production sql server databases. I have quite a few issues with blocking during these processes (mainly call sp's and some direct inserts/selects) The BizTalk server is in the same domain but in many cases seems to causes blocks on itself. I can identify these but honestly BizTalk is like SharePoint with sql server, kind of a black box. Anyone seen or know of any good practices within this environment?
October 8, 2013 at 4:08 am
Curious are extracts from BizTalk as source to "some SQL Server" destination? Although not recommended, but seems to help is using (nolock) hint. Was not sure from message if BizTalk or T-SQL issue from destination SQL Server.
--------------------------------------------------
...0.05 points per day since registration... slowly crawl up to 1 pt per day hopefully 😀
October 8, 2013 at 7:15 am
the source is hl7 sending messages to sql server tables for processing
October 10, 2013 at 2:43 am
timscronin (10/8/2013)
the source is hl7 sending messages to sql server tables for processing
I can identify these but honestly BizTalk is like SharePoint with sql server, kind of a black box. Anyone seen or know of any good practices within this environment?
Would the blocking happen to be occurring in the msgboxdb?
--------------------------------------------------
...0.05 points per day since registration... slowly crawl up to 1 pt per day hopefully 😀
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply