Cross Transactions between ADO & ADO.Net

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


.

Relevant Pages

  • Re: Cross Transactions between ADO & ADO.Net
    ... connection--it thrashes the server unnecessarily and discards useful server ... goes away and quietly reopen the connection when they return. ... > DTC transactions are not only heavy, they might also cause deadlocks due ... We even call ADO ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Cross Transactions between ADO & ADO.Net
    ... MARS session pool limited to one connection?). ... > There is one thing that might help here, if you're using SQL Server. ... We even call ADO code from ... >> the DTC cordinator from COM+ to handle the transactions between ADO.Net ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Cross Transactions between ADO & ADO.Net
    ... DTC transactions are not only heavy, they might also cause deadlocks due to ... And also I wouldn't recommend keeping an open connection to the sql server ... > some code will be ADO & some code will be ADO.Net. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: ADO MSSQL7 and two independent transactions
    ... No, ADO connection corresponds to OLEDB session, not to OLEDB data source. ... I dont want nested transactions, ...
    (borland.public.delphi.database.ado)
  • Re: Transactions in Access 2000
    ... DAO ones do. ... I need to use transactions to make sure data is consistent. ... like ADO as to make the db as portable between Access versions ... ADO you shouldn't have a portability problem. ...
    (comp.databases.ms-access)
Loading