SQL Server 2005 Ізноў intoduced спосаб адкату транзакцыі ў SQL Server, 2005
НАБОР НА XACT_ABORT
калі XACT_ABORT на. T-SQL заявы аўтаматычна адкат транзакцыі, калі адбылася памылка ў справаздачнасці.
НАБОР НА XACT_ABORT
Выкарыстанне Emp
Пачніце Tran
Устаўце ў EmpInfo значэння(1)
Устаўце ў EmpInfo значэння(1) — Гэта заява будзе падняць першасны ключ памылку
Устаўце ў EmpInfo значэння(2)
Фіксацыя Tran
Першая лінія даного будзе выконвацца без якіх-небудзь памылак. Першасны ключ памылка падняць на другой лініі. Але ўся здзелка блок не будзе здзейсніў таму, што XACT_ABORT у на.
You should note that XACT_ABORT terminates the current *batch*, not the entire command. Batches are separated with the GO keyword. Execution will continue at the beginning of the next batch.
This feature is also in SQL Server 2000, though it behaves slightly differently for various errors.
In SQL 2000, there are cases where XACT_ABORT fails to rollback the transaction automatically.
For instance:
Inserting into an invalid column name.
Inserting into a primary key with IDENTITY_INSERT OFF.
Executing a SELECT that uses a non-existent UDF.
These types of errors are usually due to a poorly authored command, so they don’t occur in the day-to-day operation of your program unless someone alters the schema. But I account for their possibility when authoring database update scripts when deploying a new version of a project, just in case deployment doesn’t go as planned.
There are ways to handle these errors. Your COMMIT should be in the batch performing the DML statements. After the batch (after the GO keyword) you can check the @@TRANCOUNT to see if it’s greater than zero and act accordingly. Usually ROLLBACK the transaction.
Transactions can span batches, so you can execute a rollback in a subsequent batch.