With a nested transaction, a commit does not write any changes to disk, except for the top level transaction. A rollback, however works regardless of the level of the transaction, so yes, it will roll the inner transaction back.
More Related Contents:
- SQL Server: Isolation level leaks across pooled connections
- Do I really need to use “SET XACT_ABORT ON”?
- TSQL Try / Catch within Transaction or vice versa?
- What happens if you don’t commit a transaction to a database (say, SQL Server)?
- Subquery in select not working in SQL Server
- Storing images in SQL Server?
- Escape a string in SQL Server so that it is safe to use in LIKE expression
- Limitations of SQL Server Express
- SQL time difference between two dates result in hh:mm:ss
- Storing files in SQL Server
- What is the best way to truncate a date in SQL Server?
- Dynamic SQL (passing table name as parameter)
- Dapper.NET and stored proc with multiple result sets
- “order by newid()” – how does it work?
- T-SQL Dynamic SQL and Temp Tables
- How to determine total number of open/active connections in ms sql server 2005
- Tablix: Repeat header rows on each page not working – Report Builder 3.0
- ORDER BY DATE showing NULLS first then most recent dates
- How can I determine in SQL Server if a dateTime range overlaps another
- How to split a string after specific character in SQL Server and update this value to specific column
- Avoid Naming User Stored Procedures SP% or SP_%
- SQL Server Configuration Manager cannot be found
- How to prevent SQL Server LocalDB auto shutdown?
- How can I run just the statement my cursor is on in SQL Server Management Studio?
- Set database collation in Entity Framework Code-First Initializer
- How do you get to limits of 8060 bytes per row and 8000 per (varchar, nvarchar) value?
- What does the SQL # symbol mean and how is it used?
- How do you deal with blank spaces in column names in SQL Server?
- Oracle sequence but then in MS SQL Server
- ODBC Call Failed with stored procedure – Pass through query