- SAP Adaptive Server – the brand name for SAP relational database management
system (RDBMS) software products.
-
SAP® Adaptive Server® Enterprise manages
multiple, large relational databases for high-volume online
transaction processing (OLTP) systems and client
applications.
-
SAP® IQ manages multiple, large relational
databases with special indexing algorithms to support
high-speed, high-volume business intelligence, decision
support, and reporting client applications.
-
SAP® 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 DBMS and RDBMS.
- atomic materialization – a materialization method that copies subscription data
from a primary 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. See also
bulk materialization and nonatomic
materialization.
- BCP utility – a feature that improves SAP Replication
Server performance when replicating large batches of insert statements
on the same table in SAP Adaptive Server Enterprise supported versions.
SAP Replication Server implements bulk copy-in in Data Server Interface
(DSI), the SAP Replication Server module responsible for sending
transactions to replicate databases, using the SAP Open Client Open
Server™ Bulk-Library. See also bulk copy.
- bulk copy – an Open Client™ interface for the high-speed
transfer of data between a database table and program variables. Bulk
copying provides an alternative to using SQL insert and select commands
to transfer data.
- bulk 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.
For example, data may be transferred from a primary database using media
such as magnetic tape, diskette, CDROM, or optical storage disk. Bulk
materialization involves a series of commands, starting with define
subscription. See also atomic materialization and
nonatomic materialization.
- client – 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.
- client application – software that is responsible for the user interface,
including menus, data entry screens, and report formats. See also client.
- commit – an instruction to the DBMS to make permanent the
changes requested in a transaction. See also transaction.
Contrast with rollback.
- database – a collection of data with a specific structure
(or schema) for accepting, storing, and providing data for users.
See also data server, DBMS,
and RDBMS.
- database connection – a connection that allows SAP Replication
Server or Replication Agent to manage the database and send or receive
transactions from or to a database. Each database in a replication
system can have only one database connection in SAP Replication Server
and one primary database connection in Replication Agent. See also
SAP Replication Server and route.
- data client – a client application that provides access to data
by connecting to a data server. See also client, client
application, and data server.
- data distribution – 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.
- data replication – the process of copying primary data to remote locations and synchronizing the copied data with the primary
data. Data replication is different from data distribution. Replicated
data is a stored copy 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.
- data server – 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 also be
any data repository with the interface and functionality a data
client requires. See also client, client
application, and data client.
- datatype – 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.
- DBMS – 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
standalone data server system. Compare with RDBMS.
- Direct Load Materialization – an automatic materialization method
to consume data between different primary and replicate databases. Data is
loaded directly from a primary table into a replicate table, no
materialization queue is used. See also materialization,
atomic materialization, bulk materialization,
and nonatomic materialization.
- ERSSD – Embedded Replication Server System Database
The SAP SQL Anywhere database that stores
Replication Server system tables. You can choose whether to store SAP
Replication Server system tables on the ERSSD or the SAP Adaptive Server
Enterprise RSSD. See also SAP Replication Server.
- failback – a procedure that restores the normal user and
client access to a primary database, after a failover procedure
switches access from the primary database to a replicate database. See
also failover.
- failover – a procedure that switches user and client access
from a primary database to a replicate database, particularly in the
event of a failure that interrupts operations at the primary database,
or access to the primary database. Failover is an important fault-tolerance
feature for systems that require high availability. See also failback.
- function – a data server object that represents an operation or set of
operations. SAP Replication Server distributes operations to replicate
databases as functions. See also stored procedure.
- function string – a string that SAP Replication Server uses to map a
function and its parameters to a data server API. Function strings allow
SAP Replication Server to support heterogeneous replication, in which
the primary and replicate databases are different types, with different
SQL extensions and different command features. See also
function.
- gateway – connectivity software that allows two or more
computer systems with different network architectures to communicate.
- inbound queue – a stable queue managed by SAP Replication Server to
spool messages received from a Replication Agent. See also
outbound queue and stable queue.
- interfaces file – a file containing entries that define
network access information for server programs in an SAP client/server
architecture. Server programs may include SAP Adaptive Servers,
gateways, Replication Servers, and Replication Agents. The interfaces
file entries enable clients and servers to connect to each other in a
network. See also Open Client and Open
Server.
- isql – an Interactive SQL client application that can connect
and communicate with any SAP® Open Server™ application,
including SAP Adaptive Server Enterprise, Replication Agent, and SAP
Replication Server. See also Open Client and Open
Server.
- Java – an object-oriented programming language developed by
Oracle (formerly Sun Microsystems). A platform-independent, “write once,
run anywhere” programming language.
- JVM – Java Virtual Machine
the JVM is the part of the Java Runtime Environment
(JRE) that is responsible for interpreting Java byte codes. See also
Java and JRE.
- JDBC – Java Database Connectivity
JDBC is the standard communication protocol for
connectivity between Java clients and data servers. See also data
server and Java.
- JRE – Java Runtime Environment
the JRE consists of the Java Virtual Machine (JVM), the
Java Core Classes, and supporting files. The JRE must be installed on a
machine to run Java applications, such as Replication Agent. See also
Java VM.
- LAN – 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.
- latency – 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.
In disk replication, latency is the time elapsed between a
disk write operation that changes a block or page on a primary device
and the disk write operation that changes the replicated block or
page on a replicate device.
See also transaction
replication.
- LOB – large object
a large collection of data stored as a single entity in
a database.
- Log Reader – an internal component of Replication Agent that
interacts with the primary database to capture transactions for
replication. See also Log Transfer Interface and
LTM.
- LTI – Log Transfer Interface
an internal component of Replication Agent that
interacts with SAP Replication Server to forward transactions for
distribution to Replication Server. See also Log Reader and
LTM.
- LTL – Log Transfer Language
a subset of the Replication Command Language
(RCL). A Replication Agent such as RepAgent uses LTL commands to submit
to SAP Replication Server the information it retrieves from primary
database transaction logs. See also Log Reader and
LTI.
- LTM – Log Transfer Manager
an internal component of Replication Agent that
interacts with the other Replication Agent internal components to
control and coordinate Replication Agent operations. See also Log
Reader and LTI.
- maintenance user – a special user login name in the replicate database that
SAP Replication Server uses to apply replicated transactions to the
database. See also replicate database and SAP
Replication Server.
- materialization – 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.
- MPR – Multi-Path Replication™
SAP
Replication Server feature that improves performance by enabling
parallel paths of data from the source database to the target database.
You can configure multi-path replication in warm standby and multisite
availability (MSA) environments. These multiple paths process data
independently of each other and are applicable when sets of data can be
processed in parallel without transactions consistency requirements
between them while still maintaining data consistency within a path, but
not adhering to the commit order across different paths.
- nonatomic materialization – 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. Contrast with atomic
materialization. See also bulk
materialization.
- ODBC – Open Database Connectivity
an industry-standard communication protocol for clients
connecting to data servers. See also client, data
server, and JDBC.
- Open Client – an SAP product that provides customer applications,
third-party products, and other SAP products with the interfaces needed
to communicate with Open Server applications. See also Open
Server.
- Open Client application – An application that uses SAP Open Client libraries to
implement Open Client communication protocols. See also Open
Client and Open Server.
- SAP Open Server – an SAP product that provides the tools and interfaces
required to create a custom server. See also Open
Client.
- Open Server application – a server application that uses SAP Open Server libraries
to implement Open Server communication protocols. See also Open
Client and Open Server.
- outbound queue – a stable queue managed by SAP Replication Server to
spool messages to a replicate database. See also inbound
queue, replicate database, and stable
queue.
- primary data – the data source
used for replication. Primary data is stored and managed by the
primary database. See also primary database.
- 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 data in a replication system. Sometimes called the
active database. Contrast with replicate database.
See also primary data.
- primary key – a column or set of columns that uniquely identifies each row in a table.
- primary site – the location or facility at which primary data
servers and primary databases are deployed to support normal business
operations. Sometimes called the active site or main site. See also primary
database and replicate site.
- primary table – a table used as a source for replication. Primary
tables are defined in the primary database schema. See also primary
data and primary database.
- primary transaction – a transaction that is committed in the primary
database and recorded in the primary database transaction log. See
also primary database, replicated transaction,
and transaction log.
- quiesce – to cause a system to go into a state in which
further data changes are not allowed. See also quiescent.
- quiescent – a state in which log scanning has stopped
and all scanned records have been propagated to their destinations in a
replication system. Some Replication Agent and SAP Replication Server
commands require that you first quiesce the replication system.
In a database, a state in which all data updates are suspended
so that transactions cannot change any data, and the data and log
devices are stable.
This term is interchangeable with quiesced and in quiesce.
See also quiesce.
- RASD – Replication Agent System Database
Information in the RASD is used by the primary database
to recognize database structure or schema objects in the transaction
log.
- RCL – Replication Command Language
the command language used to manage SAP Replication
Server. See also SAP Replication Server.
- RDBMS – relational database management system
an application that manages and controls relational
databases. Compare with DBMS. See also relational
database.
- 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.
- replicate data – 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.
- replicate database – 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 data
in a replication system. Contrast with primary database. See
also replicate data, replicated
transaction, and replication system.
- replicated transaction – 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.
- replicate site – the location or facility at which replicate data
servers and replicate databases are deployed to support normal business operations during scheduled downtime at the
primary site. Contrast with primary site. See also replicate
database.
- Replication Agent – 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 an
SAP Replication Server for distribution to a replicate database. See
also primary database and SAP Replication
Server.
- replication definition – a description of a table or stored procedure in a
primary database, for which subscriptions can be created. The
replication definition, maintained by SAP Replication Server, includes
information about the columns to be replicated and the location of the
primary table or stored procedure. See also SAP Replication
Server and subscription.
- replication system – 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 transaction
replication.
- rollback – an instruction to a database to back out of the
changes requested in a unit of work (called a transaction). Contrast
with commit. See also transaction.
- route – A one-way message stream from a primary SAP Replication
Server to a replicate SAP Replication Server. Routes carry data-changing
commands (including those for RSSDs) and replicated functions (database
procedures) between separate SAP Replication Servers. See also SAP
Replication Server.
- RSSD – Replication Server System Database
the SAP Adaptive Server Enterprise (SAP ASE)
database containing an SAP Replication Server system tables. The user
can choose whether to store Replication Server system tables on SAP ASE
or embedded in an SAP SQL Anywhere database hosted by SAP Replication
Server. See also SAP Replication Server.
- SAP Replication Server – an SAP software product that provides the infrastructure for a
transaction replication system. See also Replication
Agent.
- SQL – Structured Query Language
a nonprocedural programming language used to process
data in a relational database. ANSI SQL is an industry standard. See
also transaction.
- stable queue – a disk device-based, store-and-forward queue managed by
SAP Replication Server. Messages written into the stable queue remain
there until they can be delivered to the appropriate process or
replicate database. SAP Replication Server provides a stable queue for
both incoming messages (the inbound queue) and outgoing messages (the
outbound queue). See also database connection, SAP
Replication Server, and route.
- stored procedure – a data server object that represents an operation or set of operations. This term is often used interchangeably with function.
- subscription – a request for SAP 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 SAP
Replication Server.
- table – in a relational DBMS, 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
for the table. See also database.
- transaction – 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 SQL.
- transactional consistency – A condition in which all transactions in the primary
database are applied in the replicate database, and in the same order
that they were applied in the primary database.
- transaction log – generally, the log of transactions that affect the data
managed by a data server. Replication Agent reads the transaction log to
identify and acquire the transactions to be replicated from the primary
database. See also Replication Agent, primary
database, and SAP Replication Server.
- transaction replication – a data replication method that copies data-changing
operations from a primary database to a replicate database. See also data replication.
- UDB – IBM DB2 Universal Database (formerly IBM DB2 for Linux, UNIX, and
Windows).
- WAN – wide-area network
a system of local-area networks (LANs) connected
together with data communication lines. Contrast with
LAN.