Transactions Lock

Transactions

Capture Transaction Details. Create database objects, such as triggers and shadow tables, to record changes to all tables belonging to the transaction. Coarse Grained Lock. Lock a set of related objects with a single lock. Implicit Lock. Use framework code to acquire locks on behalf of code that accesses shared resources. Optimistic Offline Lock. Ensure that changes made by one session do not conflict with changes made by another session. Pessimistic Offline Lock. Prevent conflicts by forcing a transaction to obtain a lock on data before using it. Transaction Script. Organize the business logic for each transaction in a single procedure, making calls directly to the database or through a thin database wrapper.