A replicated function, associated with a function replication definition, that Replication Server delivers from a primary database to a subscribing replicate database. An applied function passes parameter values to a stored procedure that is executed at the replicate database. See also replicated function delivery, request function, and function replication definition.
A method of replicating, from a source to a destination database, a stored procedure that is associated with a table replication definition.
A command that a client submits when the client is not prevented from proceeding with other operations before the completion status is received. Many Replication Server commands function as asynchronous commands within the replication system.
A materialization method that copies subscription data from a primary database to a replicate database through the network in a single atomic operation, using a select operation with a holdlock. No changes to primary data are allowed until data transfer is complete. Replicate data may be applied either as a single transaction or in increments of ten rows per transaction, which ensures that the replicate database transaction log does not fill. Atomic materialization is the default method for the create subscription command. See also nonatomic materialization, bulk materialization, and no materialization.
A setting applied to replication definitions, using the set autocorrection command, to prevent failures caused by missing or duplicate rows in a copy of a replicated table. When autocorrection is enabled, Replication Server converts each update or insert operation into a delete followed by an insert. Enable autocorrection only for replication definitions whose subscriptions use non atomic materialization.
A function-string class that does not inherit function strings from a parent class. See also function-string class.
A type of subscription that replicates rows based on bitmap comparisons. Create columns using the int datatype, and identify them as the rs_address datatype when you create a replication definition. When you create a subscription, compare each rs_address column to a bitmask using a bitmap comparison operator (&) in the where clause. Rows that match the subscription’s bitmap are replicated.
A materialization method whereby subscription data in a replicate database is initialized outside of the replication system. For example, data may be transferred from a primary database using media such as magnetic tape, CD, or optical storage disk. Bulk materialization involves a series of commands, starting with define subscription. You can use bulk materialization for subscriptions to table replication definitions or function replication definitions. See also atomic materialization, nonatomic materialization, and no materialization.
See error class and function-string class.
A set of function-string classes, consisting of two or more levels of derived and parent classes that derive from the same base class. See also function-string class.
A program connected to a server in a client/server architecture. A may be a front-end application program executed by a user, or a utility program that executes as an extension of the system.
The Sybase interface standard for programs executing in a client/server architecture.
A connection from a Replication Server to a database. See also Data Server Interface (DSI).
Connection profiles allow you to configure your connection with a pre-defined set of properties.
A set of database dumps or transaction dumps that is synchronized across multiple sites by distributing an rs_dumpdb or rs_dumptran function through the replication system.
A set of related data tables and other objects that is organized and presented to serve a specific purpose.
A description of a set of database objects—tables, transactions, functions, system stored procedures, and DDL—for which a subscription can be created.
You can also create table replication definitions and function replication definitions. See also table replication definition and function replication definition.
A server program, such as Sybase Adaptive Server Enterprise, that provides database management services to clients.
The set of commands in a query language, such as Transact-SQL, that describes data and their relationships in a database. DDL commands in Transact-SQL include those using the create, drop, and alter keywords.
The set of commands in a query language, such as Transact-SQL, that operates on data. DML commands in Transact-SQL include select, insert, update, and delete.
A server whose client interface conforms to the Sybase Client/Server Interfaces and provides the functionality necessary to maintain the physical representation of a replicated table in a database. Data servers are usually database servers, but they can also be any data repository with the interface and functionality Replication Server requires.
Replication Server threads that correspond to a connection between a Replication Server and a database. DSI threads submit transactions from the DSI outbound queue to a replicate data server. They consist of a scheduler thread and one or more executor threads. The scheduler thread groups the transactions by commit order and dispatches them to the executor threads. The executor threads map functions to function strings and execute the transactions in the replicate database. DSI threads use an Open Client connection to a database. See also outbound queue and connection.
A specific combination of a database management system (DBMS) product such as a relational or non-relational data server, a database residing in that DBMS, and the communication method used to access that DBMS from other parts of a replication system. See also database and data server.
The datatype of the value delivered to the Replication Server from the Replication Agent:
If the Replication Agent delivers a base Replication Server datatype (such as datetime) to the Replication Server, the declared datatype is the base datatype.
Otherwise, the declared datatype must be the user-defined datatype (UDD) for the original datatype at the primary database.
The function string that is provided by default for the system-provided classes rs_sqlserver_function_class and rs_default_function_class and classes that inherit function strings from these classes, either directly or indirectly. See also function string.
The optional process when a subscription is dropped, whereby specific rows that are not used by other subscriptions are removed from the replicate database.
A function-string class that inherits function strings from a parent class. See also function-string class and parent class.
A database system where data is stored in multiple databases on a network. The databases may be managed by data servers of the same type (for example, Adaptive Server) or by heterogeneous data servers.
A Replication Server thread (DIST) that helps to determine the destination of each transaction in the inbound queue.
A message written by Adaptive Server in a database transaction log when a dump is performed. In a warm standby application, when you are initializing the standby database with data from the active database, you can specify Replication Server to use the dump marker to determine where in the transaction stream to begin applying transactions in the standby database.
An integrated set of software applications and connectivity tools that allow access to data within a heterogeneous database environment, such as a variety of LAN-based, non-ASE data sources, and mainframe data sources.
A set of libraries that can be used to provides direct communication between Replication Server and an Oracle database.
A Replication Server response to a data server error. Possible Replication Server error actions are ignore, warn, retry_log, log, retry_stop, and stop_replication. Error actions are assigned to specific data server errors.
A name for a collection of data server error actions that are used with a specified database.
A Replication Server object that represents a data server operation, such as insert, delete, select, or begin transaction. Replication Server distributes such operations to other Replication Servers as functions. Each function consists of a function name and a set of data parameters. To execute the function in a destination database, Replication Server uses function strings to convert a function to a command or set of commands for a type of database. See also user-defined and replicated function delivery.
A description of a replicated function used in replicated function delivery. The function replication definition, maintained by Replication Server, includes information about the parameters to be replicated and the location of the primary version of the affected data. See also replicated function delivery.
The range of a function’s effect. Functions have replication definition scope or function-string class scope. A function with replication definition scope is defined for a specific replication definition and cannot be applied to other replication definitions. A function with function-string class scope is defined once for a function-string class and is available only within that class.
A string that Replication Server uses to map a database command to a data server API. For the rs_select and rs_select_with_lock functions only, the string contains an input template, used to match function strings with the database command. For all functions, the string also contains an output template, used to format the database command for the destination data server.
A named collection of function strings used with a specified database connection. Function-string classes include those provided with Replication Server and those you have created. Function-string classes can share function string definitions through function-string inheritance. See also base class, class tree, derived class, function-string inheritance, and parent class.
The ability to share function string definitions between classes, whereby a derived class inherits function strings from a parent class. See also derived class, function-string class, and parent class.
An identifier used in a function string to represent a value that is to be substituted at runtime. Variables in function strings are enclosed in question marks (?). They represent column values, function parameters, system-defined variables, or user-defined variables.
A subscription to a function replication definition (used in applied function delivery).
Connectivity software that allows two or more computer systems with different network architectures to communicate.
Data servers that are supplied by more than one vendor used together in a distributed database system.
A file containing entries that define network access information for server programs in a Sybase client/server architecture. Server programs may include Adaptive Servers, SQL Servers, gateways, Replication Servers, and Replication Agents such as LTM for SQL Server. The interfaces file entries enable clients and servers to connect to each other in a network.
The measure of the time it takes to distribute to a replicate database a data modification operation first applied in a primary database. The time includes Replication Agent processing, Replication Server processing, and network overhead.
The value stored in the rs_locater table of the Replication Servers RSSD that identifies the latest log transaction record received and acknowledged by the Replication Server from each previous site during replication.
The name that a user or a system component such as Replication Server uses to log in to a data server, Replication Server, or Replication Agent.
A subset of the Replication Command Language (RCL). A Replication Agent such as RepAgent or LTM for SQL Server uses LTL commands to submit to Replication Server the information it retrieves from primary database transaction logs.
The Replication Agent program for Sybase SQL Server. See also Replication Agent and Replication Agent thread.
A data server login name that Replication Server uses to maintain replicate data. In most applications, maintenance user transactions are not replicated.
Copying data specified by a subscription from a primary database to a replicate database, thereby initializing the replicate table. Replicate data can be transferred over a network, or, for subscriptions involving large amounts of data, loaded initially from media. See also atomic materialization, bulk materialization, no materialization, and nonatomic materialization.
A stable queue used to spool messages related to a subscription being materialized or dematerialized.
Methodology for replicating database objects—tables, functions, transactions, system stored procedures, and DDL from the primary to the replicate database. See also database replication definition.
A materialization method that copies subscription data from a primary to a replicate database through the network in a single operation, without a holdlock. Changes to the primary table are allowed during data transfer, which may cause temporary inconsistencies between replicate and primary databases. Data is applied in increments of ten rows per transaction, which ensures that the replicate database transaction log does not fill. Nonatomic materialization is an optional method for the create subscription command. See also autocorrection, atomic materialization, no materialization, and bulk materialization.
Secure transmission of data across a network. Replication Server supports third-party security mechanisms that provide user authentication, unified login, and secure message transmission between Replication Servers.
A materialization method that lets you create a subscription when the subscription data already exists at the replicate site. Use the create subscription command with the without materialization clause. Use the no-materialization method to create subscriptions to table replication definitions and function replication definitions. See also atomic materialization and bulk materialization.
A database client application characterized by frequent transactions involving data modification (inserts, deletes, and updates).
Formed by the Replication Agent, the queue ID (qid) uniquely identifies each log record passed to the Replication Server. It includes the date and time from the primary data server, and the database generation number.
A stable queue used to spool messages. The DSI outbound queue spools messages to a replicate database. The RSI outbound queue spools messages to a replicate Replication Server.
A method of configuring a database connection so that transactions are applied to a replicate data server using multiple DSI threads operating in parallel, rather than a single DSI thread. See also connection and Data Server Interface (DSI).
An identifier representing a value that is provided when a procedure executes. Parameter names are prefixed with an @ character in function strings. When a procedure is called from a function string, Replication Server passes the parameter values, unaltered, to the data server. See also searchable parameter.
A function-string class from which a derived class inherits function strings. See also function-string class and derived class.
The definitive version of a set of data in a replication system. The primary data is maintained on a data server that is known to all of the Replication Servers with subscriptions for the data.
Any database that contains data that is replicated to another database through the replication system.
The user who starts an application. When using network-based security, Replication Server logs in to remote servers as the principal user.
A group of articles from the same primary database. A publication lets you collect replication definitions for related tables and stored procedures and then subscribe to them as a group. Collect replication definitions as articles in a publication at the source Replication Server and subscribe to them with a publication subscription at the destination Replication Server.
A subscription to a publication. See also publication.
The datatype of the column after the column-level translation (and before a class-level translation, if any) at the replicate data server. The published datatype must be either a Replication Server base datatype or a UDD for the datatype in the target data server. If the published datatype is omitted from the replication definition, it defaults to the declared datatype
In a database management system, a request to retrieve data that meets a given set of criteria. The SQL database language includes the select command for queries.
A replication system in which all data-changing operations (or transactions) have been propagated to their destinations. Some Replication Server commands or procedures require that you first quiesce the replication system.
A request to execute a procedure that resides in a remote server. The server that executes the procedure be an Adaptive Server, a Replication Server, or a server created using Open Server. The request can originate from any of these servers or from a client application. The RPC request format is a part of the Sybase Client/Server Interfaces.
The Replication Agent for Adaptive Server Enterprise. The Replication Agent thread is an Adaptive Server thread. It sends transaction log information from the primary database to the primary Replication Server.
The thread on a Replication Server database connection that a Replication Agent connects with, on behalf of a primary database. See also Data Server Interface (DSI).
Any database that contains data that is replicated from another database through the replication system.
A method of replicating, from a source to a destination database, a stored procedure that is associated with a function replication definition. See also applied function, request function, and function replication definition.
An Adaptive Server stored procedure that is marked as replicated using the sp_setrepproc or the sp_setreplicate system procedure. Replicated stored procedures can be associated with function replication definitions or table replication definitions. See also replicated function delivery and asynchronous procedure delivery.
A table that is maintained by Replication Server, in part or in whole, in databases at multiple locations. There is one primary version of the table, which is marked as replicated using the sp_setreptable or the sp_setreplicate system procedure; all other versions are replicated copies.
A program or module that sends transaction log information from a primary data server to a primary Replication Server. Sybase provides separate Replication Agent software products to support non-ASE data servers in a replication system.
Usually, a description of a table 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 version of the table.
You can also create function replication definitions; sometimes the term “table replication definition” is used to distinguish between table and function replication definitions. See also function replication definition.
The Sybase server program that maintains replicated data, typically on a LAN, and processes data transactions received from other Replication Servers on the same LAN or on a WAN.
A thread that logs in to a destination Replication Server and transfers commands from the RSI outbound stable queue to the destination Replication Server. There is one RSI thread for each destination Replication Server that is a recipient of commands from a primary or intermediate Replication Server. See also outbound queue.
The system administrator who manages routine operations in the Replication Server.
The Adaptive Server database containing a Replication Server system tables. You can choose whether to store Replication Server system tables on the RSSD or the Adaptive Server® Anywhere (ASA) ERSSD.
The Adaptive Server with the database containing a Replication Servers system tables (the RSSD).
A data processing system where data is replicated in multiple databases to provide remote users with the benefits of local data access. Specifically, a replication system that is based on Replication Server and includes other components, such as Replication Agents and data servers.
A replicated function, associated with a function replication definition, that Replication Server delivers from a replicate database to a primary database. A request function passes parameter values to a stored procedure that is executed at the primary database. See also replicated function delivery, request function, and function replication definition.
The process whereby column value changes in rows in a primary version of a table cause corresponding rows in a replicate version of the table to be inserted or deleted, based on comparison with values in a subscription’s where clause.
The structure of the database. DDL commands and system procedures change system tables stored in the database. Supported DDL commands and system procedures can be replicated to standby databases when you use Replication Server version 11.5 or later and Adaptive Server version 11.5 or later.
A column in a replicated table that can be specified in the where clause of a subscription or article to restrict the rows replicated at a site.
A parameter in a replicated stored procedure that can be specified in the where clause of a subscription to help determine whether or not the stored procedure should be replicated. See also parameter.
See truncation point.
An installation consisting of, at minimum, a Replication Server, data server, and database, and possibly a Replication Agent, usually at a discrete geographic location. The components at each site are connected over a WAN to those at other sites in a replication system.
The version number for an individual Replication Server. Once the site version has been set to a particular level, the Replication Server enables features specific to that level, and downgrades are not allowed. See also software version, and system version.
The version number of the software release for an individual Replication Server. See also site version and system version.
A thread that manages the stable queues. There is one Stable Queue Manager (SQM) thread for each stable queue accessed by the Replication Server, whether inbound or outbound.
A thread that reassembles transaction commands in commit order. A Stable Queue Transaction (SQT) interface thread reads from inbound stable queues, puts transactions in commit order, then sends them to the Distributor (DIST) thread or a DSI thread, depending on which thread required the SQT ordering of the transaction.
Store-and-forward queues where Replication Server stores messages destined for a route or database connection. Messages written into a stable queue remain there until they can be delivered to the destination Replication Server or database. Replication Server builds stable queues using its disk partitions. See also outbound queue, and materialization queue.
A collection of SQL statements and optional control-of-flow statements stored under a name in an Adaptive Server database. Stored procedures supplied with Adaptive Server are called system procedures. Some stored procedures for querying the RSSD are included with the Replication Server software.
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. You can also subscribe to a function replication definition, for replicating stored procedures.
See dematerialization.
See materialization.
See row migration.
A graphical tool that provides a common interface for managing products. Replication Server uses Replication Server Manager as a Sybase Central plug-in.
A command that a client considers complete only after the completion status is received.
A function that is predefined and part of the Replication Server product. Different system functions coordinate replication activities, such as rs_begin, or perform data manipulation operations, such as rs_insert, rs_delete, and rs_update.
The error class includes non-ASE error classes and the function-string classes that Replication Server provides. Function strings are generated automatically for the system-provided function-string classes and for any derived classes that inherit from these classes, directly or indirectly. See also error class and function-string class.
The version number for a replication system that represents the version for which new features are enabled, for Replication Servers of 11.0.2 or earlier, and below which no Replication Server can be downgraded or installed. For a Replication Server version 11.5, use of certain new features requires a site version of 1150 and a system version of at least 1102. See also site version, and software version.
A process running within Replication Server. Built upon Sybase Open Server, Replication Server has a multi-threaded architecture. Each thread performs a certain function such as managing a user session, receiving messages from a Replication Agent or another Replication Server, or applying messages to a database. See also Data Server Interface (DSI), Distributor, and Replication Server Interface (RSI).
A mechanism for grouping statements so that they are treated as a unit: either all statements in the group are executed or no statements in the group are executed.
The relational database language used with Adaptive Server. Transact-SQL is based on standard SQL (Structured Query Language), with Sybase extensions.
An Adaptive Server database that holds primary data has an active truncation point, marking the transaction log location where Adaptive Server has completed processing. This is the primary truncation point.
The Replication Agent for an Adaptive Server database maintains a secondary truncation point, marking the transaction log location separating the portion of the log successfully submitted to the Replication Server from the portion not yet submitted. The secondary truncation point ensures that each operation enters the replication system before its portion of the log is truncated.
A function that allows you to create custom applications that use Replication Server to distribute replicated functions or asynchronous stored procedures between sites in a replication system. In replicated function delivery, a user-defined function is automatically created by Replication Server when you create a function replication definition.
See site version, software version, and system version.
