Cannot Use Save Transaction Within A Distributed Transaction Error
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up avoid “Cannot use SAVE TRANSACTION within a distributed transaction” error between SQL 2005 and 2008 up vote 2 down vote favorite 1 in our production environment we have a stored procedure (in sql 2005 server) that import data into a local table from a remote stored procedure (stored in a remote sql 2008). The code is like this: insert <
distributed transaction If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 2 of 2 Thread: Cannot use SAVE TRANSACTION within a distributed transaction Tweet Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode May 21st, 2002,04:56 AM #1 MarathonMan View Profile View Forum Posts Thread Starter New Member Join Date May 2002 Location Hertfordshire, UK Posts 3 Cannot use http://stackoverflow.com/questions/16546849/avoid-cannot-use-save-transaction-within-a-distributed-transaction-error-betwe SAVE TRANSACTION within a distributed transaction I am running some Data-Centric and User-Centric components in a COM+ application. The Data-Centric components have Requires Transaction on them - they have the setcomplete and setabort in them The user centric components do not. They do not call set complete and set abort - they just instantiate the data-centric components and of course the data-centric components take care of the transactions - or so I thought ! I http://www.vbforums.com/showthread.php?172245-Cannot-use-SAVE-TRANSACTION-within-a-distributed-transaction get this error ..... " [Microsoft][ODBC SQL Server Driver][SQL SERVER]Cannot use SAVE TRANSACTION within a distributed transaction " I have a SAVE point in a transaction in a stored procedure and I suspect this is conflicting with COM+ transactions - is it possible in any way to have SAVE points in stored procedures being called by transactional COM+ Data Centric components??? Many many thanks !!!! Reply With Quote May 22nd, 2002,01:34 PM #2 jamesf View Profile View Forum Posts New Member Join Date May 2002 Posts 2 I have run into the same problem and think that you may be on the right track in thinking that the sprocs transaction is conflicting with COM+. Just for giggles, I set the transaction level for the object in COM+ to supported instead of required, and this seemed to help on some of the objects...but this is not really a permanent solution in my case. What is odd is that if I run the app in vb without reference to COM+, it works great. If I run the app as compiled dlls registered on a local machine, it works great, which does seem to point to a COM+ conflict. Have you tried removing the transaction altogether from the sproc as I have not tried this yet? I will be interested to hear if you solved the
from GoogleSign inHidden fieldsSearch for groups or messages