I'm glad one of our biztalk devs is very cooperative today 😉
Scenarion 1 : add begin tran ... commit tran
Just encapsulating the trigger with its own Begin tran ... commit tran, off course didn't do the trick.
Because: that tran is just an augmentation of the @@trancount which - because of the "set implicit transactions on" >0 at that time.
When I added a while loop :crazy:
while @@trancount > 0
begin
commit tran
end
resulted in a failure of the biztalk apps.
Scenario 2: set transaction isolation level read committed
IMO this one would be plausible, but once again, it resulted in messages like
Process ID 61 attempted to unlock a resource it does not own: DATABASE: 7 Retry the transaction, because this error may be caused by a timing condition. If the problem persists, contact the database administrator.
and sqlserver got itself messed up once again.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me