>I've been using Transaction processing (BEGIN TRANSACTION, END TRANSACTION, ROLLBACK) for a while now, but still not sure I fully understand when, why, and how to use it properly. Specifically, why would I use nested transactions? Also, is there a limit to the number of updates within a transaction.
I have not read about a limit. I suggest you do the test yourself: start the transaction, make changes to 5,000 or 10,000 records, and end the transaction. Repeat the test with ROLLBACK.
Also check the time taken: please note that any record that participates in the transaction is implicitly locked - therefore, the transaction should take the least amount of time possible.
Nested transactions, AFAIK, allow for the use of procedures. For instance, RI code will start and end a transactions - but when the RI-code is automatically invoked, you may alread be in a transaction.
HTH, Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
