tag:blogger.com,1999:blog-495177919198719500.post5737610264773020600..comments2023-12-27T20:52:29.483-08:00Comments on Microsoft Sql Server Tutorials: Rollback Nested Transactions in Stored Procedure - SQL ServerSuprotim Agarwalhttp://www.blogger.com/profile/08349831623922214390noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-495177919198719500.post-38751957184311263062013-09-11T11:58:29.536-07:002013-09-11T11:58:29.536-07:00SQL server does not support nested transactions.
...SQL server does not support nested transactions.<br /><br />http://youtu.be/MGFfQyJMO9EAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-495177919198719500.post-47528162898829899262011-10-16T19:35:52.061-07:002011-10-16T19:35:52.061-07:00Named Transactions is Ok for a DB with operations ...Named Transactions is Ok for a DB with operations that are not logged frequently. But for me it is not an option here as the database I work on has operations that are bulk logged. So they would be blocked anyways and would lead to errors.Suprotim Agarwalhttps://www.blogger.com/profile/08349831623922214390noreply@blogger.comtag:blogger.com,1999:blog-495177919198719500.post-70479548359420640232011-10-16T12:11:55.937-07:002011-10-16T12:11:55.937-07:00So a "....ASP.NET Architecture MVP, MCSD, MCA...So a "....ASP.NET Architecture MVP, MCSD, MCAD, MCDBA, MCSE, is the CEO of A2Z Knowledge Visuals Pvt..." doesn't know how to get rid of the error "Transaction count after EXECUTE". What is this then, a graphomania? :-) <br />Re-throw the original message before rollback or use named transactions, right? LOL.Anonymousnoreply@blogger.com