1.0.2.c Terminology Used in this Guide Following are some common terms used throughout this document, and a brief definition for each. Microsoft SQL Server/SQL Server/SQL Database Server - Terms used to describe the machine with the Microsoft SQL Server software installed on which a Microsoft SQL database is configured. This machine will serve as the target of the replication (i.e., the Primary Production Server).Primary Production Server - This is the Microsoft SQL Server that will serve as the “source” of the Replication (i.e., the machine being replicated).Standby Server - This is the machine that is configured to serve as the destination of the replication (i.e., data is replicated from the Primary Production Server to this machine).“Live” vs. “Idle” - These two terms refer to the intended “end result” state of the Standby Server. If the system is to be set up so that it can immediately assume the role of a new Microsoft SQL Server upon failure of the Primary Production Server, it is considered “Live”. If the Standby Server is intended to serve simply as a target for replicated data (e.g., individual SQL database data is to be stored on the machine for later recovery to the Primary Production Server), it is considered “Idle”.Replication Sets (“Repsets”) - Repsets define the relationship between hosts and data sets that are to be replicated. A repset contains information that defines which machine is serving as the Primary Production Server (the replication “source”), and which machine is acting as the Standby Server (the replication “destination”). A Repset must consist of one source and at least one destination.Replication Scheme - This phrase is used to describe all of the systems involved in the replication process (e.g., a Primary Production Server replicating its Microsoft SQL Database data to a Standby Server would constitute a “Replication Scheme”).