What is an MTS Transaction?
| Author |
Message |
|
Kip Fryma
#1 / 10
|
 What is an MTS Transaction?
Could someone enlighten me to what is consider a transaction in MTS and why
you need to use MTS for transactions when ADO provides this
functionality....
|
| Tue, 27 Jan 2004 23:48:52 GMT |
|
 |
|
Paul Browe
#2 / 10
|
What is an MTS Transaction? MTS does it better.
Quote: > Could someone enlighten me to what is consider a transaction in MTS and
why
> you need to use MTS for transactions when ADO provides this
> functionality....
|
| Wed, 28 Jan 2004 00:03:40 GMT |
|
|
|
Chris Heywoo
#3 / 10
|
What is an MTS Transaction? A transaction is an action or a group of actions performed on a database which either happen or don't happen, check "ACID" (can't remember what it stands for, just the acronym).
Quote: > Could someone enlighten me to what is consider a transaction in MTS and
why
> you need to use MTS for transactions when ADO provides this
> functionality....
|
| Wed, 28 Jan 2004 00:02:52 GMT |
|
|
|
Chuck Haeberl
#4 / 10
|
What is an MTS Transaction? Several reasons: As stated in another reply, MTS does do it better...here's why:
1) Multiple database transaction synchronization WITH NO CODE EFFORT
2) Transactional processing handled in the object model - again, NO CODE
EFFORT
With MTS, especially if you're updating multiple databases, its far simpler
to design your object model around the requried transactions and forget all
that messy ADO transaction management code. Create a connection, execute an
action ,and if anything goes wrong you call one line of code:
GetObjectContext.SetAbort.
That rolls everything back that happened in that context. If you don't call
SetAbort, commit is implied.
What a Transaction in MTS is, fundamentally? A transaction IS the object
model. You make a call into a COM+ component set up to require a
transaction, and all subsequent calls within that COM+ library are included
in the transaction, unless you configure them to either not support or
require a new transaction, in which case behavior, of course, varies.
If you find you must manipualte complex data in one call, MTS is the best
way I know to make that job easy.
Quote: > Could someone enlighten me to what is consider a transaction in MTS and
why
> you need to use MTS for transactions when ADO provides this
> functionality....
|
| Wed, 28 Jan 2004 00:52:29 GMT |
|
|
|
Kip Fryma
#5 / 10
|
What is an MTS Transaction? Are you saying that if in the following procedure I create an ObjectContext and then do the following: Delete a record from an ADO recordset...
Create a text file...
Make a registry entry...
and then I call SetAbort..
the whole thing will be rolled back so there is no text file made, no record
deleted, and no regestry entry made.....
How?
Or is it just a way to handle ADO object transactions?
Quote: > Several reasons: > As stated in another reply, MTS does do it better...here's why:
> 1) Multiple database transaction synchronization WITH NO CODE EFFORT
> 2) Transactional processing handled in the object model - again, NO CODE
> EFFORT
> With MTS, especially if you're updating multiple databases, its far
simpler
> to design your object model around the requried transactions and forget
all
> that messy ADO transaction management code. Create a connection, execute
an
> action ,and if anything goes wrong you call one line of code:
> GetObjectContext.SetAbort.
> That rolls everything back that happened in that context. If you don't
call
> SetAbort, commit is implied.
> What a Transaction in MTS is, fundamentally? A transaction IS the object
> model. You make a call into a COM+ component set up to require a
> transaction, and all subsequent calls within that COM+ library are
included
> in the transaction, unless you configure them to either not support or
> require a new transaction, in which case behavior, of course, varies.
> If you find you must manipualte complex data in one call, MTS is the best
> way I know to make that job easy.
> > Could someone enlighten me to what is consider a transaction in MTS and
> why
> > you need to use MTS for transactions when ADO provides this
> > functionality....
|
| Wed, 28 Jan 2004 01:22:28 GMT |
|
|
|
Steve Parke
#6 / 10
|
What is an MTS Transaction? Not quite. The database record will be restored but the text file and registry entry will remain. MTS requires a resource manager to roll back. As far as I know there is nothing available for the registry but I think I heard of one mentioned for the file system objects. Steve
Quote: > Are you saying that if in the following procedure I create an ObjectContext > and then do the following: > Delete a record from an ADO recordset...
> Create a text file...
> Make a registry entry...
> and then I call SetAbort..
> the whole thing will be rolled back so there is no text file made, no
record
> deleted, and no regestry entry made.....
> How?
> Or is it just a way to handle ADO object transactions?
> > Several reasons:
> > As stated in another reply, MTS does do it better...here's why:
> > 1) Multiple database transaction synchronization WITH NO CODE EFFORT
> > 2) Transactional processing handled in the object model - again, NO CODE
> > EFFORT
> > With MTS, especially if you're updating multiple databases, its far
> simpler
> > to design your object model around the requried transactions and forget
> all
> > that messy ADO transaction management code. Create a connection,
execute
> an
> > action ,and if anything goes wrong you call one line of code:
> > GetObjectContext.SetAbort.
> > That rolls everything back that happened in that context. If you don't
> call
> > SetAbort, commit is implied.
> > What a Transaction in MTS is, fundamentally? A transaction IS the
object
> > model. You make a call into a COM+ component set up to require a
> > transaction, and all subsequent calls within that COM+ library are
> included
> > in the transaction, unless you configure them to either not support or
> > require a new transaction, in which case behavior, of course, varies.
> > If you find you must manipualte complex data in one call, MTS is the
best
> > way I know to make that job easy.
> > > Could someone enlighten me to what is consider a transaction in MTS
and
> > why
> > > you need to use MTS for transactions when ADO provides this
> > > functionality....
|
| Wed, 28 Jan 2004 03:02:51 GMT |
|
|
|
Kip Fryma
#7 / 10
|
What is an MTS Transaction? Ok so MTS kind of just wraps itself around the ADO rollback methods then.....
Quote: > Not quite. > The database record will be restored but the text file and registry entry > will remain. MTS requires a resource manager to roll back. As far as I > know there is nothing available for the registry but I think I heard of one > mentioned for the file system objects. > Steve
> > Are you saying that if in the following procedure I create an
> ObjectContext
> > and then do the following:
> > Delete a record from an ADO recordset...
> > Create a text file...
> > Make a registry entry...
> > and then I call SetAbort..
> > the whole thing will be rolled back so there is no text file made, no
> record
> > deleted, and no regestry entry made.....
> > How?
> > Or is it just a way to handle ADO object transactions?
> > > Several reasons:
> > > As stated in another reply, MTS does do it better...here's why:
> > > 1) Multiple database transaction synchronization WITH NO CODE EFFORT
> > > 2) Transactional processing handled in the object model - again, NO
CODE
> > > EFFORT
> > > With MTS, especially if you're updating multiple databases, its far
> > simpler
> > > to design your object model around the requried transactions and
forget
> > all
> > > that messy ADO transaction management code. Create a connection,
> execute
> > an
> > > action ,and if anything goes wrong you call one line of code:
> > > GetObjectContext.SetAbort.
> > > That rolls everything back that happened in that context. If you
don't
> > call
> > > SetAbort, commit is implied.
> > > What a Transaction in MTS is, fundamentally? A transaction IS the
> object
> > > model. You make a call into a COM+ component set up to require a
> > > transaction, and all subsequent calls within that COM+ library are
> > included
> > > in the transaction, unless you configure them to either not support or
> > > require a new transaction, in which case behavior, of course, varies.
> > > If you find you must manipualte complex data in one call, MTS is the
> best
> > > way I know to make that job easy.
> > > > Could someone enlighten me to what is consider a transaction in MTS
> and
> > > why
> > > > you need to use MTS for transactions when ADO provides this
> > > > functionality....
|
| Wed, 28 Jan 2004 03:21:00 GMT |
|
|
|
Michael D. Lon
#8 / 10
|
What is an MTS Transaction? Differently, yes. Better? That depends on the requirements of your application. Too many people use distributed transactions when they
shouldn't just because MTS programming makes it easy.
Michael D. Long
Quote: > MTS does it better.
> > Could someone enlighten me to what is consider a transaction in MTS and
> why
> > you need to use MTS for transactions when ADO provides this
> > functionality....
|
| Wed, 28 Jan 2004 05:24:33 GMT |
|
|
|
Michael D. Lon
#9 / 10
|
What is an MTS Transaction? No. There is plenty of information at msdn.microsoft.com about
what MTS is, what it does and how it works. All of it isn't
accurate, but the main points are covered.
Michael D. Long
Quote: > Ok so MTS kind of just wraps itself around the ADO rollback methods
> then.....
|
| Wed, 28 Jan 2004 05:27:06 GMT |
|
|
|
moolo
#10 / 10
|
What is an MTS Transaction? Atomicy, Consistency, Isolation, Durability http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpr... tml/acidculture.asp
Quote: > A transaction is an action or a group of actions performed on a database > which either happen or don't happen, check "ACID" (can't remember what it > stands for, just the acronym). > Chris.Heywood
> > Could someone enlighten me to what is consider a transaction in MTS and
> why
> > you need to use MTS for transactions when ADO provides this
> > functionality....
|
| Sun, 01 Feb 2004 20:42:56 GMT |
|
| |
|
