CHAPTER 8 Transactions and Versioning
295
Figure 8-3: Concurrent insertions to different tables
Data definition operations on a single table lock out all other readers and
writers from that table. See “Locks for DDL operations” for details.
Transactions use committed data
Committed data results when a write transaction commits. Every transaction
uses the latest committed version of the database as of the time the transaction
begins. It uses that version until the transaction commits.
The time a transaction begins is called its Start Timestamp. The start timestamp
can be any time before the transaction's first read. Any insertions and deletions
the transaction makes are reflected in the snapshot. Thus, for the user executing
a transaction, the image in the snapshot changes whenever that transaction
writes data to the table, and then reads it again. For all other users, the image
remains static until their transaction commits.
Summary of Contents for Adaptive Server IQ 12.4.2
Page 1: ...Administration and Performance Guide Adaptive Server IQ 12 4 2 ...
Page 16: ...xvi ...
Page 20: ...Related documents xx ...
Page 40: ...Compatibility with earlier versions 20 ...
Page 118: ...Troubleshooting startup shutdown and connections 98 ...
Page 248: ...Importing data by replication 228 ...
Page 306: ...Integrity rules in the system tables 286 ...
Page 334: ...Cursors in transactions 314 ...
Page 396: ...Users and permissions in the system tables 376 ...
Page 438: ...Determining your data backup and recovery strategy 418 ...
Page 484: ...Network performance 464 ...
Page 500: ...System utilities to monitor CPU use 480 ...
Page 514: ...Characteristics of Open Client and jConnect connections 494 ...
Page 536: ...Index 516 ...