This glossary describes ASE Replicator terms used in this book. For a description of Adaptive Server and SQL terms, refer to the Adaptive Server Glossary.
A replication scenario in which a single database acts as both a primary database and a replicate database. See also primary database and replicate database.
An ASE Replicator object that identifies a primary or replicate database. See also primary database and replicate database.
A user database residing on the same Adaptive Server with the primary databases for ASE Replicator. The Distribution Database contains the stable queue and all the metadata needed to support replication. See also stable queue.
The smallest database object entity that can be identified in an ASE Replicator system, either the column of a table or the input parameter of a stored procedure. See also primary article and replicate article.
A string value maintained by ASE Replicator that identifies a location in the stable queue or transaction log. See also stable queue and transaction log.
A data server login name that ASE Replicator uses to apply replicated transactions in a replicate database.
The process of copying data specified by a replicate article from a primary database to a replicate database, thereby initializing the replicate table, and activating the replicate article so that ASE Replicator can begin replicating data to the replicate database. See also validation and replicate article.
An ASE Replicator object that identifies a single primary database object (table or stored procedure) for which transactions will be published. See also replicate article.
A database that contains published objects (tables and stored procedures), and that is a source of transactions to be replicated. See also replicate database.
A database object (table or stored procedure) in a primary database. See also primary database.
A container object associated with a primary database connection, and which contains primary articles. See also primary database.
The process of identifying and replicating transactions from a primary database. See also subscribe.
An ASE Replicator object that identifies a single replicate database object (table or stored procedure) that subscribes to a primary article. See also primary article.
A database object (table or stored procedure) in a replicate database. See also replicate database.
A store-and-forward queue in which ASE Replicator records transaction operations to be replicated. Operations written into the stable queue remain there until they can be delivered to the replicate database. See also transaction log.
The process of selecting published transactions and identifying the replicate objects that should receive them. See also publish.
A container object associated with a replicate database connection, and that points to a specific publication. See also replicate database.
Generally, the log of transactions that affect the data managed by a database server. ASE Replicator creates a stable queue transaction log in the Distribution Database. See also stable queue.
A condition in which all transactions in the primary database are applied in the replicate database in the same order that they were applied in the primary database.