A transaction is bound by the ACID test. ACID stands for Atomicity, Consistency, Isolation (or Independence), and Durability: : TRANSACTION « Transaction « SQL Server / T-SQL Tutorial

SQL Server / T-SQL Tutorial
1. Query
2. Insert Delete Update
3. Table
4. Table Join
5. Data Types
6. Set Operations
7. Constraints
8. Subquery
9. Aggregate Functions
10. Date Functions
11. Math Functions
12. String Functions
13. Data Convert Functions
14. Analytical Functions
15. Sequence Indentity
16. View
17. Index
18. Cursor
19. Database
20. Transact SQL
21. Procedure Function
22. Trigger
23. Transaction
24. XML
25. System Functions
26. System Settings
27. System Tables Views
28. User Role
29. CLR
Java
Java Tutorial
Java Source Code / Java Documentation
Java Open Source
Jar File Download
Java Articles
Java Products
Java by API
Photoshop Tutorials
Maya Tutorials
Flash Tutorials
3ds-Max Tutorials
Illustrator Tutorials
GIMP Tutorials
C# / C Sharp
C# / CSharp Tutorial
C# / CSharp Open Source
ASP.Net
ASP.NET Tutorial
JavaScript DHTML
JavaScript Tutorial
JavaScript Reference
HTML / CSS
HTML CSS Reference
C / ANSI-C
C Tutorial
C++
C++ Tutorial
Ruby
PHP
Python
Python Tutorial
Python Open Source
SQL Server / T-SQL
Oracle PL / SQL
Oracle PL/SQL Tutorial
PostgreSQL
SQL / MySQL
MySQL Tutorial
VB.Net
VB.Net Tutorial
Flash / Flex / ActionScript
VBA / Excel / Access / Word
XML
XML Tutorial
Microsoft Office PowerPoint 2007 Tutorial
Microsoft Office Excel 2007 Tutorial
Microsoft Office Word 2007 Tutorial
SQL Server / T-SQL Tutorial » Transaction » TRANSACTION 
23. 1. 1. A transaction is bound by the ACID test. ACID stands for Atomicity, Consistency, Isolation (or Independence), and Durability:
Atomicity means that the transactions are an all-or-nothing entity carrying out all steps or none at all
Consistency ensures that the data is valid both before and after the transaction. Data integrity must be maintained (foreign key references, for exampleand internal data structures need to be in a valid state.
Isolation is a requirement that transactions not be dependent on other transactions that may be taking place concurrently (either at the same time or overlapping). One transaction can’t see another transaction’s data that is in an intermediate state, but instead sees the data as it was either before the transaction began or after.
Durability means that the transaction's effects are permanent after the transaction has committed, and any changes will survive system failures.

Quote from:
SQL Server 2005 T-SQL Recipes A Problem-Solution Approach
23. 1. TRANSACTION
23. 1. 1. A transaction is bound by the ACID test. ACID stands for Atomicity, Consistency, Isolation (or Independence), and Durability:
23. 1. 2. Explicit Transaction Commands
23. 1. 3. Using Transactions
23. 1. 4. BEGIN TRANSACTION
23. 1. 5. Using Explicit Transactions
23. 1. 6. Forcing an exclusive table lock.
23. 1. 7. Transaction spread across batches:
23. 1. 8. Exception before transaction committing
23. 1. 9. statements coded as a transaction
23. 1. 10. A script with nested transactions
23. 1. 11. One batch that contains two transactions
23. 1. 12. What happens with stored proc transactions and exceptions?
23. 1. 13. Declare variable in a transaction
23. 1. 14. Inserting a Row into MyTable and Rolling Back the Transaction
www.java2java.com | Contact Us
Copyright 2009 - 12 Demo Source and Support. All rights reserved.
All other trademarks are property of their respective owners.