|
- concurrency - What is a database transaction? - Stack Overflow
A transaction is a unit of work that you want to treat as "a whole " It has to either happen in full or not at all A classical example is transferring money from one bank account to another To do that you have first to withdraw the amount from the source account, and then deposit it to the destination account The operation has to succeed in full If you stop halfway, the money will be lost
- How to rollback a transaction in a stored procedure?
Looking at the SQL Server Books Online, Microsoft seems to have an (incorrect) method of handling nested transactions in a stored procedure: Nesting Transactions Explicit transactions can be
- sql server - How to use SqlTransaction in C# - Stack Overflow
There is an Update query in progress, the Transaction is started at a higher level on the connection In order to ensure that all server data is in a valid state for the Update, I need to do a couple reads
- How to rollback or commit a transaction in SQL Server
The good news is a transaction in SQL Server can span multiple batches (each exec is treated as a separate batch ) You can wrap your EXEC statements in a BEGIN TRANSACTION and COMMIT but you'll need to go a step further and rollback if any errors occur
- writing a transaction in t-sql and error handling - Stack Overflow
Do u think there is a better way to write a transaction in t-sql? Is there a better approach that improves maintainability and performance of the application that uses this transaction? -- Descri
- Correct use of transactions in SQL Server - Stack Overflow
Add a try catch block, if the transaction succeeds it will commit the changes, if the transaction fails the transaction is rolled back:
- The transaction log for the database is full - Stack Overflow
I have a long running process that holds open a transaction for the full duration I have no control over the way this is executed Because a transaction is held open for the full duration, whe
- What happens if you dont commit a transaction to a database (say, SQL . . .
As long as you don't COMMIT or ROLLBACK a transaction, it's still "running" and potentially holding locks If your client (application or user) closes the connection to the database before committing, any still running transactions will be rolled back and terminated
|
|
|