I'm using the "Old API". As I've learnt from this topic
, the standard way of calling stored procedures makes such calls wrapped in a commited transaction. Therefore calling a stored procedure that contains transactions makes some exception raised (the suggested way of calling such procedures is using direct ADO.NET API). On the other hand, if this procedure doesn't contain transactions but raises some error, updates made by this procedure are commited by this wrapping transaction.
All that seems to make the following scenario impossible:
b. some updates using the scope
c. a stored procedure call that makes its own updates
We would like to have all updates rolled back but as a result we have changes made in b. rolled back but changes made in c. still commited.
Is it true that mixing scope-level and sproc-level updates is - while using "Old API" - impossible (as far as using transactions is concerned)? Does the "New API" makes such a feature available?