This glossary describes Replication Server and Replication Agent terms used in this book.
The brand name for Sybase relational database management system (RDBMS) software products.
Adaptive Server Enterprise manages multiple, large relational databases for high-volume online transaction processing (OLTP) systems and client applications.
Adaptive Server IQ manages multiple, large relational databases with special indexing algorithms to support high-speed, high-volume business intelligence, decision support, and reporting client applications.
SQL Anywhere (formerly Adaptive Server Anywhere) manages relational databases with a small DBMS footprint, which is ideal for embedded applications and mobile device applications.
See also database and RDBMS.
A materialization method that copies subscription data from a primary database to a replicate database in a single, atomic operation. No changes to primary data are allowed until the subscription data is captured at the primary database. See also bulk materialization and nonatomic materialization.
A bulk copy transfer utility that provides the ability to load multiple rows of data into a table in a target database. See also bulk copy.
An Open Client interface for the high-speed transfer of data between a database table and program variables. It provides an alternative to using SQL insert and select commands to transfer data. See also BCP utility and materialization.
A materialization method whereby subscription data in a replicate database is initialized outside of the replication system. You can use bulk materialization for subscriptions to table replication definitions or function replication definitions. See also atomic materialization, materialization, and nonatomic materialization.
In client/server systems, the part of the system that sends requests to servers and processes the results of those requests. See also client application.
Software that is responsible for the user interface, including menus, data entry screens, and report formats. See also client.
An instruction to the DBMS to make permanent the changes requested in a transaction. Contrast with rollback. See also DBMS and transaction.
A client application that provides access to data by connecting to a data server. See also client, client application, and data server.
A method of locating (or placing) discrete parts of a single set of data in multiple systems or at multiple sites. Data distribution is distinct from data replication, although a data replication system can be used to implement or support data distribution. Contrast with data replication.
The process of copying data to remote locations, and then keeping the replicated data synchronized with the primary data. Data replication is distinct from data distribution. Replicated data is stored copies of data at one or more remote sites throughout a system, and it is not necessarily distributed data. Contrast with data distribution. See also transaction replication.
A server that provides the functionality necessary to maintain the physical representation of a table in a database. Data servers are usually database servers, but they can be any data repository with the interface and functionality a data client requires. See also client, client application, and data client.
A collection of data with a specific structure (or schema) for accepting, storing, and providing data for users. See also data server and relational database.
A connection that allows Replication Server to manage the database and distribute transactions to the database. Each database in a replication system can have only one database connection defined in Replication Server. See also Replication Server and route.
A keyword that identifies the characteristics of stored information on a computer. Some common datatypes are: char, int, smallint, date, time, numeric, and float. Different data servers support different datatypes.
An abbreviation for database management system, a computer-based system for defining, creating, manipulating, controlling, managing, and using databases. The DBMS can include the user interface for using the database, or it can be a stand-alone data server system. Compare with RDBMS. See also database.
An abbreviation for embedded Replication Server System Database, which manages replication system information for a Replication Server.
A Replication Server object that represents a data server operation, such as insert, delete, or begin transaction. Replication Server distributes operations to replicate databases as functions. See also function string.
A string that Replication Server uses to map a function and its parameters to a data server API. Function strings allow Replication Server to support replication between (homogeneous) non-Sybase data servers, and heterogeneous replication, in which the primary and replicate databases are different types, with different SQL extensions and different command features. See also function.
Connectivity software that allows two or more computer systems with different network architectures to communicate.
A stable queue managed by Replication Server to spool messages received from a Replication Agent. See also outbound queue and stable queue.
A file containing information that Sybase Open Client and Open Server applications need to establish connections to other Open Client and Open Server applications. See also Open Client and Open Server.
An interactive SQL client application that can connect and communicate with any Sybase Open Server application, including Adaptive Server Enterprise, Replication Agent, and Replication Server. See also Open Client and Open Server.
An object-oriented, platform-independent, “write once, run anywhere” programming language developed by Sun Microsystems. The Replication Agent is a Java application.
The Java Virtual Machine (JVM), which is the part of the Java Runtime Environment (JRE) that interprets Java byte codes. See also Java and JRE.
An abbreviation for Java Database Connectivity, the standard communication protocol for connectivity between Java clients and data servers. See also client, data server, and Java.
The Sybase JDBC driver that Replication Agent uses to connect to Replication Server and the RSSD.
An abbreviation for Java Runtime Environment, which consists of the Java Virtual Machine (Java VM or JVM), the Java Core Classes, and supporting files. To run a Java application, such as the Replication Agent, a JRE must be installed on the machine. See also Java and Java VM.
An abbreviation for “local area network,” a computer network located on the user premises and covering a limited geographical area (usually a single site). Communication within a local area network is not subject to external regulations; however, communication across the LAN boundary can be subject to some form of regulation. Contrast with WAN.
In transaction replication, the time it takes to replicate a transaction from a primary database to a replicate database. Specifically, latency is the time elapsed between committing an original transaction in the primary database and committing the replicated transaction in the replicate database. See also transaction replication.
An abbreviation for large object, a type of data element (or datatype) associated with a column that contains extremely large quantities of data.
An internal component of the Replication Agent that interacts with the primary database to capture transactions for replication. See also Log Transfer Interface and Log Transfer Manager.
An internal component of the Replication Agent that interacts with Replication Server to forward transactions for distribution to a replicate database. See also Log Reader and Log Transfer Manager.
An internal component of the Replication Agent that interacts with Replication Server to forward transactions for distribution to a replicate database. See also Log Reader and Log Transfer Manager.
The proprietary protocol used between Replication Agent and Replication Server to replicate data from the primary database to Replication Server. See also Log Reader and Log Transfer Interface.
A special user login name in the replicate database that Replication Server uses to apply replicated transactions to the database. See also replicate database and Replication Server.
The process of copying the data from a primary database to a replicate database, initializing the replicate database so that the replication system can begin replicating transactions. See also atomic materialization, bulk materialization, and nonatomic materialization.
A materialization method that copies subscription data without a lock on the primary database. Changes to primary data are allowed during data transfer, which may cause temporary inconsistencies between the primary and replicate databases. Contrast with atomic materialization. See also bulk materialization.
An abbreviation for Open Database Connectivity, an industry standard communication protocol for clients connecting to data servers. See also client, data server, and JDBC.
A Sybase product that provides customer applications, third-party products, and other Sybase products with the interfaces needed to communicate with Open Server applications. See also Open Server.
An application that uses Sybase Open Client libraries to implement Open Client communication protocols. See also Open Client and Open Server.
A Sybase product that provides the tools and interfaces required to create a custom server. See also Open Client.
A server application that uses Sybase Open Server libraries to implement Open Server communication protocols. See also Open Client and Open Server.
A stable queue managed by Replication Server to spool messages to a replicate database. See also inbound queue, replicate database, and stable queue.
The version of a set of data that is the source used for replication. Primary data is stored and managed by the primary database. See also primary database.
The database that contains the data to be replicated to another database (the replicate database) through a replication system. The primary database is the source of replicated transactions and data in a replication system. Sometimes called the active database. Contrast with replicate database. See also primary data and replicated transaction.
A table used as a source for replication. Primary tables are defined in the primary database schema. See also primary data and primary database.
A transaction that is committed in the primary database and recorded in the primary database transaction log. See also primary database and transaction log.
To cause a system to go into a state in which further data changes are not allowed. See also quiescent.
In a replication system, a state in which all data-changing operations have been propagated to their destinations. Some Replication Server commands require that you quiesce the replication system.
In a database, a state in which all data-changing operations are suspended so that transactions cannot change any data.
This term is interchangeable with quiesced and in quiesce. See also quiesce.
An abbreviation for Replication Agent System Database, information in which the primary database uses to recognize database structure or schema objects in the transaction log.
An abbreviation for Replication Command Language, the command language used to manage Replication Server. See also Replication Server.
An abbreviation for relational database management system, which is an application that manages and controls relational databases. Compare with DBMS. See also relational database.
A collection of data in which data is viewed as being stored in tables, which consist of columns (data items) and rows (units of information). Relational databases can be accessed by SQL requests. Compare with database. See also SQL.
The data managed by a replicate database, which is the destination (or target) of a replication system. Contrast with primary data. See also replicate database and replication system.
A database that contains data replicated from another database (the primary database) through a replication system. The replicate database is the database that receives replicated transactions and/or data in a replication system. Sometimes called the standby database. Contrast with primary database. See also replicate data, replicated transaction, and replication system.
A set of data that is replicated from a primary database to a replicate database by a replication system. See also primary database, replication system, and replicate database.
A primary transaction that is replicated from a primary database to a replicate database by a transaction replication system. See also primary database, primary transaction, replicate database, and transaction replication.
An application that reads a primary database transaction log to acquire information about data-changing transactions in the primary database, processes the log information, and then sends it to a Replication Server for distribution to a replicate database. See also primary database, replicate database, and Replication Server.
A description of a table or stored procedure in a primary database, for which subscriptions can be created. The replication definition, maintained by Replication Server, includes information about the columns to be replicated and the location of the primary table or stored procedure. See also Replication Server and subscription.
The Sybase software product that provides the infrastructure for a robust transaction replication system. See also Replication Agent.
An abbreviation for Replication Server System Database, which manages replication system information for a Replication Server. See also Replication Server.
A data processing system that replicates data from one location to another. Data can be replicated between separate systems at a single site, or from one or more local systems to one or more remote systems. See also data replication and transaction replication.
An instruction to a database to reverse the data changes requested in a unit of work (a transaction). Contrast with commit. See also transaction.
A one-way message stream from a primary Replication Server to a replicate Replication Server. Routes carry data-changing commands (including those for RSSDs) and replicated functions (database procedures) between separate Replication Servers. See also Replication Server.
An abbreviation for Structured Query Language, a nonprocedural programming language used to process data in a relational database. ANSI SQL is an industry standard. See also transaction.
A disk device-based, store-and-forward queue managed by Replication Server. Messages written into the stable queue remain there until they can be delivered to the appropriate process or replicate database. Replication Server provides a stable queue for both incoming messages (the inbound queue) and outgoing messages (the outbound queue). See also database connection, Replication Server, and route.
A request for Replication Server to maintain a replicated copy of a table, or a set of rows from a table, in a replicate database at a specified location. See also replicate database, replication definition, and Replication Server.
In a relational database, a two-dimensional array of data, or a named data object that contains a specific number of unordered rows composed of a group of columns that are specific to the table. See also database and relational database.
A unit of work in a database that can include zero, one, or many operations (including insert, update, and delete operations), and that is either applied or rejected as a whole. Each SQL statement that modifies data can be treated as a separate transaction, if the database is so configured. See also replicated transaction and SQL.
Generally, the log of transactions that affect the data managed by a database or a data server. Replication Agent reads the transaction log to identify and acquire the transactions to be replicated from the primary database. See also primary database, Replication Agent, and transaction.
A data replication method that copies data-changing operations from a primary database to a replicate database. See also data replication, primary database, and replicate database.
