But in oracle it seems tha. 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. Is there a better approach that improves maintainability and performance of the application that uses this transaction Shouldn't begin transaction [tran1] be placed inside try
Note that there is only the need to rollback in the case of some exception or timeout or other general failure, there would not be a conditional reason to rollback. 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. If your caller starts a transaction and the calee hits, say, a deadlock (which aborted the transaction), how is the callee going to communicate to the caller that the transaction was aborted and it should not continue with 'business as usual' This is my first time writing transaction, is it correct/best practice to have the try/catch block inside the transaction or should the transaction be inside the try block? In my case, it turned out the disk that sql server was installed on was full and the transaction log couldn't be expanded
Msg 9002, level 17, state 4, line 1 the transaction log for database 'mydb' is full due to 'active_transaction' And it did not delete a thing What does that message mean How can i delete the records?
OPEN
