Error: Transaction context in use by another session
My setup went smoothly. I create a new sp on datatabase server, "Comit Changes" then I can see it in TFS. I run into error when I modified the sp from TFS, then go to SQL Source Control and do try to "get Latest". First I got error MSDTC not available, I then started MSDTC services, now i got different error "Transaction context in use by another session". Can you help?
Thanh Nguyen
shared this idea
Given the age of this request, I’m assuming that you either managed to get things working, or gave up. I’m very sorry we didn’t respond earlier, but if by any chance you’re still struggling with this, please contact support@red-gate.com and they’ll be able to help.
-
Adrian Tompkins
commented
Rather than having it fail I exported the head to a scripts folder and used SQL Compare to deploy. In SQL Compare there is an option to turn off transactions altogether. I would agree that having the isolation level as an option would be preferable though. Possibly even at the object level.
-
Jason
commented
We see this frequently because we have a lot of views that use linked servers. We currently work around it by waiting for it to fail, then editing the script to use "READ COMMITTED" instead of "SERIALIZABLE" as the isolation level. I'd love a way to set the transaction level up front (or remove it entirely) to make this easier.