Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 348
  • Last Modified:

COM+ transactions

Created a DLL Using VB6 to run under COM+.

If I set the MTSTransactionMode property for the class to 1 - NoTransactions, what effect will this have if my class method calls a SQL Server stored procedure which does a series of updates which in turn are wrapped in a T-SQL BEGIN TRANSACTION/COMMIT TRANSACTION ??
  • 2
1 Solution
Good question,

See this one it may not help you but it's worth to check out


Be my guess, You still can do it from ADO if you set to

Don't accept this as an answer because I want to know the answer too

It creates another transaction begins and commits its work regardless of your transaction in COM+ component. e.g. It does not affect your transaction, does not commits or rollbacks your transaction.
jonatecAuthor Commented:
To. iozturk...
Does that mean if I start a transaction thru COM+, (Required), that my SQL BEGIN TRANSACTION is ignored because SQL did not start the transaction? Presumably in this situation the ROLLBACK TRANSACTION will still be recongnised by SQL?
No, They create seperate transactions. COM+ object (require), say obj1, creatres a transaction, when you call your SP from COM+ object that does not support transaction, say obj2, SP(stored proc.) creates another db transaction commits or rollbacks and this operation does not commit or rollback obj1's transaction. And if obj1 commits or rollbacks also this has no effect on SP transaction.
Be carefull if you set transactions also from Component services applet. Its settings overrides settings of objects.

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now