Replication is the duplication of table schema and data from a source database to a destination database. There are two basic replication models, tight consistency and loose consistency.
Tight consistency is a replication model that guarantees that all copies will be constantly identical to the original. It requires a high-speed LAN, reduces database availability, and is a less scalable model than one based on loose consistency. This is implemented today through the use of two-phase commit. (For information on implementing two-phase commit for SQL Server 6.0, see Microsoft SQL Server Programming DB-Library for C.)
Loose consistency is a replication model that allows a time lag between the moment when original data is altered and when the replicated copies of that data are updated. It does not guarantee that all copies will be constantly identical to the original. An advantage of loose consistency is that it supports LANs, WANs, fast and slow communication links, and intermittently connected databases. It allows better database availability and is much more scalable than a tight consistency model. SQL Server 6.0 replication is based on a loose consistency model.
SQL Server 6.0 replication has these fundamental characteristics:
See the topics that follow for more information about each of these features.