Re: Transaction with stored procedure
- From: "Jim Underwood" <james.underwood@xxxxxxxxxxxxxxxx>
- Date: Thu, 3 Nov 2005 15:24:32 -0500
I see...
You could try using linked servers/remote servers to do the updates from one
stored proc, but that can cause more problems.
Here is one approach I used when trying to update two databases, one oracle
and one SQL Server...
I started a transaction (oracle stored procedure) against the one database.
If the transaction succeeded, I executed the (SQL) stored procedure against
the second database. If the second (SQL) transaction succeeded, I commited
the first (oracle) transaction. If it failed I rolled back the transaction.
not sure if this is at all helpful. Unfortunately I no longer have the code
that I used for this either.
"ucasesoftware" <ucasesoftware@xxxxxxxxxx> wrote in message
news:1131048761.767849.204250@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> negative
>
> cause one of the 3 are in another database
>
.
- Follow-Ups:
- Re: Transaction with stored procedure
- From: ucasesoftware
- Re: Transaction with stored procedure
- References:
- Re: Transaction with stored procedure
- From: ucasesoftware
- Re: Transaction with stored procedure
- Prev by Date: All tabs spread throughout Tab Control
- Next by Date: Stop Form Update
- Previous by thread: Re: Transaction with stored procedure
- Next by thread: Re: Transaction with stored procedure
- Index(es):
Relevant Pages
|