The create database replication definition syntax has been modified to
allow the
in files parameter to accept an include table list.
Syntax
create database replication definition <db_repdef>
with primary at <server_name.db>
[not replicate DDL] |
[replicate DDL [{{with | without} auto_update_table_list} |
{{with | without} auto_extend_table_list}]]
[[not] replicate functions <setcont>]
[[not] replicate transactions <setcont>]
[[not] replicate system procedures <setcont>]
[[not] replicate tables [[<setcont> [except <setcont>]] | in files ([<file1> [, <file2> [, ..]]])]
[[not] replicate {SQLDML | DML_options} [in <table_list>]]
[user <username> password <pass>]]
setcont ::= [[in] ([<owner1>.]<name1>[, [<owner2>.]<name2> [, ... ]])]
Usage
- The order of the files in the in files parameter’s file list
sets the materialization order. All the tables in the first file in the list
materialize—in the order in which they are listed in the file—before tables in
the second file begin to materialize, and so on.
- If a table in any file fails to materialize, SAP Replication Server finishes
materializing all the other tables in that file, but does not move on to the
next file.
- If a table occurs
in
more than
one
file,
only
the first occurrence triggers materialization.
- If a table is
later
added to the replication
definition
using the alter database replication
definition
command, the file
will
not be
updated.
- The
user who starts the primary Replication Server must have read permission for the
files in the in files parameter’s file
list.