Transaction Flow in Sql Server 2005
Every transaction moves through the various checks and code in the following order:
1. Identity insert check.
2. Nullability constraint.
3. Data-type check.
4. Instead of trigger execution. If an instead of trigger exists, execution of the DML
stops here. Instead of triggers are not recursive. Therefore, if the insert trigger executes
a DML command that fires the same event (insert, update or delete), then the
instead of trigger will be ignored the second time around.
5. Primary-key constraint.
6. Check constraints.
7. Foreign-key constraint.
8. DML execution and update to the transaction log.
9. After trigger execution.
10. Commit transaction.
11. Writing the data file.
Hope it Helps .
Happy Coding!!!
1. Identity insert check.
2. Nullability constraint.
3. Data-type check.
4. Instead of trigger execution. If an instead of trigger exists, execution of the DML
stops here. Instead of triggers are not recursive. Therefore, if the insert trigger executes
a DML command that fires the same event (insert, update or delete), then the
instead of trigger will be ignored the second time around.
5. Primary-key constraint.
6. Check constraints.
7. Foreign-key constraint.
8. DML execution and update to the transaction log.
9. After trigger execution.
10. Commit transaction.
11. Writing the data file.
Hope it Helps .
Happy Coding!!!