|
- 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
- sql server - SQL Transaction was deadlocked - Stack Overflow
Sometimes I get this kind of exception on not very busy SQL server: Transaction (Process ID 57) was deadlocked on lock resources with another process and has been chosen as the deadlock victim Re
- The transaction log for database tempdb is full due to ACTIVE . . .
@GiulioCaccin Thank you for the suggestion, but I ran a query on the transaction logs and the log space used for tempdb is only at 31% The other inquiry you referred me to also doesn't help me to understand why the temp objects I create refuse to be dropped or created Unless there's something that I am missing from your suggestion
- Isolation Level - Serializable. When should I use this?
From MSDN regarding SET TRANSACTION ISOLATION LEVEL: SERIALIZABLE Places a range lock on the data set, preventing other users from updating or inserting rows into the data set until the transaction is complete This is the most restrictive of the four isolation levels Because concurrency is lower, use this option only when necessary
- Row was updated or deleted by another transaction (or unsaved-value . . .
optimistic locking consists in detecting that another transaction has updated deleted the same row, and throwing the exception you're getting in this case If you have a version field, you're already using optimistic locking, and this is what throws the exception Pessimistic locking will make your application slow and subject to deadlocks
- How to check active transactions in SQL Server 2014?
DBCC OPENTRAN displays information about the oldest active transaction and the oldest distributed and nondistributed replicated transactions, if any, within the transaction log of the specified database Results are displayed only if there is an active transaction that exists in the log or if the database contains replication information
- Sql server - log is full due to ACTIVE_TRANSACTION
Sql server - log is full due to ACTIVE_TRANSACTION [duplicate] Asked 11 years, 2 months ago Modified 8 years, 3 months ago Viewed 367k times
- Correct use of transactions in SQL Server - Stack Overflow
Shouldn't BEGIN TRANSACTION [Tran1] be placed inside TRY? Anyway - very simple and elegant piece of code
|
|
|