This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.
The RollbackTransaction method ends a unit of work explicitly opened by a corresponding BeginTransaction method call, discarding any change(s) applied within the work unit.
Use the BeginTransaction, CommitTransaction, and RollbackTransaction methods to implement application-defined transaction units.
When unqualified by the optional argument, the RollbackTransaction method undoes an entire transaction. Use the SaveTransaction method to set transaction midpoints, then specify the most recent midpoint in the SavePoint argument to undo only those changes applied after the point in the transaction. For more information, see SaveTransaction Method.
|SQL Distributed Management Objects (SQL-DMO) implements objects that can be used to automate Microsoft SQL Server administration. Most administrative functions use data definition language (DDL) statements for their implementation. Generally, application-defined transaction units are not respected by DDL. Where SQL Server does not implement transaction space for DDL, SQL-DMO does not extend DDL by defining a transaction space.|
In general, use the BeginTransaction, CommitTransaction, and RollbackTransaction methods only when submitting Transact-SQL command batches for execution by using methods such as ExecuteImmediate. It is suggested that you do not leave transaction units open but either commit or roll back the unit when the command batch execution method is complete.