In transaction shipping (e.g., used in the Sybase Replication
Server and Microsoft SQL Server), the regular transaction log
is used, instead of triggers and a special snapshot log table.
At the source site, the transaction log is sniffed to detect
updates on replicated tables, and those log records are
transferred to a replication server, which packages up the
corresponding transactions to update the replicas. Transaction
shipping has the advantage that it does not require triggers,
which can increase the workload on the operational source
databases. However, it cannot always be used easily across
DBMSs from different vendors, because there are no standard
APIs for accessing the transaction log
In transaction shipping (e.g., used in the Sybase ReplicationServer and Microsoft SQL Server), the regular transaction logis used, instead of triggers and a special snapshot log table.At the source site, the transaction log is sniffed to detectupdates on replicated tables, and those log records aretransferred to a replication server, which packages up thecorresponding transactions to update the replicas. Transactionshipping has the advantage that it does not require triggers,which can increase the workload on the operational sourcedatabases. However, it cannot always be used easily acrossDBMSs from different vendors, because there are no standardAPIs for accessing the transaction log
การแปล กรุณารอสักครู่..