The events captured for replication through a Sybase replication system are referred to as transactions, even though they might not correspond directly to an actual transaction in the primary database. For example, if a transaction affects both marked tables and unmarked tables, only the operations that affect the marked tables are captured for replication. Operations on unmarked tables are ignored.
All data-change operations captured for replication exist within a transaction context. That is, only committed transaction operations are replicated; transactions that are rolled back are not replicated.
Even though the data-change events replicated through a Sybase replication system are really operations, those operations are grouped in an atomic collection, and they represent the results of a committed transaction in the primary database.
