If a source table name is long and you generate an audit log table name with the default suffix of _LOG based on the source schema, the audit log table name might be too long. You can define a shorter suffix.
Alternatively, you can use a blank log suffix. However, if you use a blank suffix in Merge Apply mode, you must use different schemas to generate regular target tables and audit log tables.
For Netezza targets, you cannot use different schemas to generate regular target tables and audit log tables because a Netezza user can own only one schema. Therefore, do not use a blank suffix for Netezza audit log tables.
On the
Runtime Settings
tab >
Calculated Columns
view, replace the default audit table name suffix of _LOG with a shorter suffix in the
Log table suffix for merge apply
field.
If you use Merge Apply mode, or if you use InitialSync with the Bulk Copy Program (BCP) to load data to SQL Server targets and need to process SQL expressions defined for source tables in SQL Apply mode, Data Replication uses this suffix to determine the audit log table that corresponds to each mapped target table.
In Audit Apply mode, the Data Replication Console uses this suffix only if you map the source tables to audit log tables based on wildcard expressions or exact name matching.
Generate audit log tables based on the source table schema.
If you use Merge Apply mode and a blank log suffix, specify a schema that includes audit log tables in the