Tough Transaction Problem with Stored Procs and ADO.

  • Thread starter Thread starter LineVoltageHalogen
  • Start date Start date
L

LineVoltageHalogen

Greetings All, I was hoping that someone might be able to shed some
light on a problem I am having. In short I have an application written
in C# calling a stored proc. Without going into the reasons why (it is
long and complicated to explain) I need to create a transaction in the
stored proc that is independent of the transaction created by ADO. It
is possible that if ADO issues a rollback I may still need to commit a
chunk of code in the stored proc. I have been trying to do this with
savepoints but I am having no luck. So here is my question:
1.) Is it possible to have a stored proc called by ADO (which will
always used transactions) that has the capacity to create its own
transactions independent of the ADO transaction. Essentially, can I
override the ADO transaction with a stored proc transaction?

Any and all help would be greatly appreciated.


TFD
 
I did some legwork and it seems that save points are only meant to be
used for rollbacks and not commits. You cannot commit in the procedure
and expect it to remain if the outermost transaction (in this case ado)
issues a rollback.

thanks for your input.

TFD
 
Back
Top