I need to do a transaction on my SQL Server dB which includes a number of
database lookups, executing some code between the lookups on the results of
each
lookup, and then do a series of database inserts/updates based on both the
results and on some information passed into this transaction by CF. If
there's
a problem at any step, all of the inserts/updates have to be rolled back.
I'm using CF5.
It seems that CFTRANSACTION is the way to go.
HOWEVER, I've been told that there have been lots of problems getting
CFTRANSACTION to work on CF5, and instead migrated to doing a similar piece
of
functionality within a stored procedure, which works (and is fast).
My sub-questions to you:
[0.a] Have you ever failed to get CFTRANSACTION to work correctly in CF5?
[0.b] Have you heard of any reasons to avoid CFTRANSACTION in CF5?
[0.c] What are the main concerns of using CFTRANSACTION vs. stored
procedure
when there could be multiple CF servers hitting a remote dB? (Besides just
general delay issues with the dB being down during the CFTRANSACTION)
[0.d] Which would you do (CFTRANSACTION / stored procedure) for CF5?
Why?
Thanks in advance!
Cheers,
+Craig
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
