TRANSACTION IS COMMITED ANYWAY 
Author Message
 TRANSACTION IS COMMITED ANYWAY

I have one transaction (no nested transactions)  wich wrappes several
updates and inserts in one batch.
There are several stored procedures in the batch. when there is a "Server:
Msg 8114, Level 16, State 1, Procedure sp{*filter*}kDb2, Line 0
Error converting data type varchar to int " in one of procedures
transaction is commited anyway . Even though Query Analyzer shows error
description all valid Inserts after and before problem procedure are


even though the line before that generated a data type conversion error .


is not this right that TRANSACTION must
rollback everything  if there is an error in the batch?

Does anybody knows why is this happening ?



Sat, 31 Aug 2002 03:00:00 GMT  
 
 [ 1 post ] 

 Relevant Pages 

1. Auto-Done configured but transaction commited.

2. Am I asking to much of transaction handling?

3. MTS commited data when it shouldn't

4. To Transaction or Not to Transaction that is the question

5. ADODB TRANSACTION ADO ERROR No Transaction is Active

6. Why to use COM+ transaction and not just SQL Server transaction

7. Reqiured Transaction and Required New Transaction

8. Cannot connect to the transaction manager or the transaction (-2147168229)

9. ADODB TRANSACTION ADO ERROR No Transaction is Active

10. ADO Connection Transaction vs. ObjectContext Transaction

11. ADOConnection.Transaction vs. ObjectContext.Transaction

12. Transaction In Transaction

 

 
Powered by phpBB® Forum Software