Re: Cross Transactions between ADO & ADO.Net
- From: "Sahil Malik [MVP]" <contactmethrumyblog@xxxxxxxxxx>
- Date: Thu, 16 Jun 2005 10:48:57 -0400
Wow thats hitech. But I can see why that is being discouraged.
One thing you mentioned is, if you have a pending datareader, the other
cannot be used. Can this restriction be gotten around using MARS? (But isn't
MARS session pool limited to one connection?).
Sounds like a hairy solution :) but a solution nonetheless.
- Sahil Malik [MVP]
Upcoming ADO.NET 2.0 book - http://tinyurl.com/9bync
----------------------------------------------------------------------------
---------------
"Pablo Castro [MS]" <pablocas@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:uXA9OsgcFHA.3184@xxxxxxxxxxxxxxxxxxxxxxx
> There is one thing that might help here, if you're using SQL Server. This
is
> a feature that we don't advertise a lot and we've been removing the focus
> from it over time; so read on if you need this as an intermediate step
while
> you migrate your app, *not* as a long-term solution:
>
> SQL Server supports something called "bound sessions", where two
connections
> (to the same server) can be bound to the same transaction, without
involving
> a distributed transaction coordinator. Bound sessions require careful
> coordination, as while you use one (e.g. have a pending data-reader) you
> cannot use the other. If those limitations are ok with you, then you can
> find out how to use bound sessions in SQL Server Books Online (it's fairly
> easy), start by looking at the sections for "sp_getbindtoken" and
> "sp_bindsession"
>
> --
> Pablo Castro
> Program Manager - ADO.NET Team
> Microsoft Corp.
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
> "Brent" <brentwa@xxxxxxxxxxxxxxxx> wrote in message
> news:u1ChPVDcFHA.2696@xxxxxxxxxxxxxxxxxxxxxxx
> > Hi, we are changing our application from VB6 to VB.Net. This is far from
a
> > trivial upgrade. We have over 400 forms and 40 dll's. We can't just take
> > down our production application and start the whole project from
scratch.
> > We have to convert this stuff in stages. Our application design is
pretty
> > much 2-tier. We connection to SQL server when the application starts and
> > then disconnect when the application unloads. We even call ADO code from
> > our dll so transactions are scattered all over the code between dll's
and
> > the main application. I guess the problem comes in when we are upgrade
> > some code will be ADO & some code will be ADO.Net. I came up with an
idea
> > which i think would work which would be to hose both our ADO object ( a
> > wrapper we wrote for ADO) and ADO.Net wrapper in COM+. We could then use
> > the DTC cordinator from COM+ to handle the transactions between ADO.Net
&
> > plain ADO for us.
> >
> > Does anyone see a better solution. The solution i came up with would
> > require two connections to the DB and if possible we would like a
solution
> > only requiring one conneciton. We are also concerned about throughput
> > since COM+ transactions are at a layer above ADO transactions and we
don't
> > want any bottlenecks in our new code if possible. Does anyone have any
> > better solutions?
> >
> > thanks,
> > Brent
> >
>
>
.
- Follow-Ups:
- Re: Cross Transactions between ADO & ADO.Net
- From: Pablo Castro [MS]
- Re: Cross Transactions between ADO & ADO.Net
- References:
- Cross Transactions between ADO & ADO.Net
- From: Brent
- Re: Cross Transactions between ADO & ADO.Net
- From: Pablo Castro [MS]
- Cross Transactions between ADO & ADO.Net
- Prev by Date: Re: Dataset refill issue - Stalls for 30 to 40 seconds
- Next by Date: Mapping Columns w/o DataAdapter?
- Previous by thread: Re: Cross Transactions between ADO & ADO.Net
- Next by thread: Re: Cross Transactions between ADO & ADO.Net
- Index(es):
Relevant Pages
|
