<?xml version="1.0" encoding="utf-8" ?><rss version="2.0"><channel><title>Bing: Transaction Example for Journal Entry</title><link>http://www.bing.com:80/search?q=Transaction+Example+for+Journal+Entry</link><description>Search results</description><image><url>http://www.bing.com:80/s/a/rsslogo.gif</url><title>Transaction Example for Journal Entry</title><link>http://www.bing.com:80/search?q=Transaction+Example+for+Journal+Entry</link></image><copyright>Copyright © 2026 Microsoft. All rights reserved. These XML results may not be used, reproduced or transmitted in any manner or for any purpose other than rendering Bing results within an RSS aggregator for your personal, non-commercial use. Any other use of these results requires express written permission from Microsoft Corporation. By accessing this web page or using these results in any manner whatsoever, you agree to be bound by the foregoing restrictions.</copyright><item><title>sql - Transaction count after EXECUTE indicates a mismatching number of ...</title><link>https://stackoverflow.com/questions/21930156/transaction-count-after-execute-indicates-a-mismatching-number-of-begin-and-comm</link><description>Exec USPStoredProcName I get the following error: Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count = 0. I have read the answers in other such questions and am unable to find where exactly the commit count is getting messed up.</description><pubDate>Thu, 02 Apr 2026 23:25:00 GMT</pubDate></item><item><title>How do you clear the SQL Server transaction log?</title><link>https://stackoverflow.com/questions/56628/how-do-you-clear-the-sql-server-transaction-log</link><description>The transaction log contains a lot of useful data that can be read using a third-party transaction log reader (it can be read manually but with extreme effort though). The transaction log is also a must when it comes to point in time recovery, so don’t just throw it away, but make sure you back it up beforehand.</description><pubDate>Sat, 04 Apr 2026 04:10:00 GMT</pubDate></item><item><title>concurrency - What is a database transaction? - Stack Overflow</title><link>https://stackoverflow.com/questions/974596/what-is-a-database-transaction</link><description>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 ...</description><pubDate>Fri, 03 Apr 2026 10:52:00 GMT</pubDate></item><item><title>Getting "Lock wait timeout exceeded; try restarting transaction" even ...</title><link>https://stackoverflow.com/questions/5836623/getting-lock-wait-timeout-exceeded-try-restarting-transaction-even-though-im</link><description>mysql&gt; update customer set account_import_id = 1; ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction I'm not using a transaction, so why would I be getting this error? I even tried restarting my MySQL server and it didn't help. The table has 406,733 rows.</description><pubDate>Sat, 04 Apr 2026 15:02:00 GMT</pubDate></item><item><title>Transaction marked as rollback only: How do I find the cause</title><link>https://stackoverflow.com/questions/19302196/transaction-marked-as-rollback-only-how-do-i-find-the-cause</link><description>Participating transaction failed - marking existing transaction as rollback-only So I just stepped through my code to see where this line is generated and found that there is a catch block which did not throw anything.</description><pubDate>Wed, 01 Apr 2026 22:36:00 GMT</pubDate></item><item><title>The transaction log for the database is full - Stack Overflow</title><link>https://stackoverflow.com/questions/17674973/the-transaction-log-for-the-database-is-full</link><description>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...</description><pubDate>Fri, 03 Apr 2026 08:15:00 GMT</pubDate></item><item><title>What happens if you don't commit a transaction to a database (say, SQL ...</title><link>https://stackoverflow.com/questions/4896479/what-happens-if-you-dont-commit-a-transaction-to-a-database-say-sql-server</link><description>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.</description><pubDate>Wed, 01 Apr 2026 19:09:00 GMT</pubDate></item><item><title>What does a transaction around a single statement do?</title><link>https://stackoverflow.com/questions/1171749/what-does-a-transaction-around-a-single-statement-do</link><description>BEGIN TRANSACTION / COMMIT "extends" this locking functionality to the work done by multiple statements, but it adds nothing to single statements. However, the database transaction log is always written to when a database is modified (insert, update, delete). This is not an option, a fact that tends to irritate people.</description><pubDate>Fri, 03 Apr 2026 01:34:00 GMT</pubDate></item><item><title>sql server - SQL Transaction Error: The current transaction cannot be ...</title><link>https://stackoverflow.com/questions/7488149/sql-transaction-error-the-current-transaction-cannot-be-committed-and-cannot-su</link><description>I'm having a similar issue to The current transaction cannot be committed and cannot support operations that write to the log file, but I have a follow-up question. The answer there references Usi...</description><pubDate>Wed, 01 Apr 2026 18:11:00 GMT</pubDate></item><item><title>postgresql - PSQLException: current transaction is aborted, commands ...</title><link>https://stackoverflow.com/questions/10399727/psqlexception-current-transaction-is-aborted-commands-ignored-until-end-of-tra</link><description>Stay being in a transaction, but when you detect that the first SQL has failed, either rollback/re-start or commit/restart the transaction. Then you can continue failing as many SQL queries on that database connection as you want. Don't catch and ignore the Exception that is thrown when a SQL statement fails.</description><pubDate>Thu, 02 Apr 2026 20:05:00 GMT</pubDate></item></channel></rss>