|
Features
The MGA Duplica
repository owns all the replication
tables, packages, triggers associated
with running the software. The
advantages of MGA Duplica’s ‘central’
repository are:
-
A single central copy
of MGA Duplica can control multiple
schemas
-
Oracle to SQL Server
replication
-
Staggered replication
allowing you to replicate critical
data immediately and non critical data
overnight or as otherwise required
-
Simple to maintain
-
Greater security
-
Flexibility, as
separate repositories can be
maintained for each replicated schema
if desired
-
Increases performance
on the server through its unique
architecture
-
Replicates from views
to tables
Main Functions
Data replication, as
performed by MGA Duplica, involves the
‘mirroring’ of changes made to a source
database into a target database within a
specified timeframe thereby creating a
duplicate of the source database.
MGA Duplica is designed
to maintain standby databases thereby
eliminating the need to undertake
time-consuming backups. As MGA Duplica
is constantly replicating changes made
to the source database, it is also ideal
for disaster recovery, wide area network
data transfer and data warehousing
purposes.
How MGA Duplica works
MGA Duplica is installed
on the destination server and connects
over SQL*Net or Net 8 to manage
replication from one schema to another.
To replicate data, MGA Duplica creates a
small umber of database objects in the
target schema (MGA Duplica repository).
The graphical user interface allows the
user to control the replication of data
via two main tools; Replication Manager
and Replication Monitor.
Replication Manager
allows the user to create their own
suites and add tables to these suites.
The rate at which data is replicated can
be controlled by setting: time
intervals, maximum rows that can be
downloaded per run, maximum query times,
order in which tables within a suite are
replicated (to allow for parent-child
relationships) and amending the time
that the table was last updated.
Replication can be commenced or
terminated at any time on a suite level,
or conversely the entire replication
control mechanism can be turned on or
off as required. The Replication Manager
suites list can be filtered to show
specific suites, and may also be printed
for reporting purposes.
Replication Monitor
allows users to monitor data whilst it
is being replicated. Each time data is
replicated an entry is saved to an audit
log file. Any errors are recorded in an
error log file. Both the audit log and
error log may be viewed from the
Replication Monitor. These logs can be
refreshed manually or automatically at
intervals specified by the user. The
logs can be printed, with the most
recent logs also viewable as printable
graphs. Target database system resources
such as tablespace size can also be
viewed. |
