Changes to alter database replication definition

alter database replication definition db_repdef
with primary at data_server.database
{[{not replicate DDL} |
{replicate DDL [{with | without} {auto_update_table_list | auto_extend_table_list}]}] |
[not] replicate setname setcont |
[not] replicate {{SQLDML | DML_options} [in table_list]} |
[alter owner from current_table_owner to new_table_owner [for table_name]] |
[{add | remove} tables {setcont}]}
[with dsi_suspended]
[user username password pass]
setcont ::= [[in] ([owner1.]name1[, [owner2.]name2 [, ... ]])] | [in files ('file_path')]
setname ::= {tables | functions | transactions | system procedures}

• not replicate DDL – Informs Replication Server not to send DDL to subscribing databases.
• replicate DDL [{with | without} {auto_update_table_list | auto_extend_table_list}] – Informs Replication Server to send DDL to subscribing databases and whether to update or extend the table list. If you specify replicate DDL without any option, DDL is sent to the replicate database, however, the table is not added to the replication path.
• replicate DDL with auto_update_table_list – Sends DDL commands to the replicate database. For a table, if pdb_automark_tables is true, the table is automatically updated in the table list when drop table or rename table DDL commands are encountered.
• replicate DDL without auto_update_table_list – Sends DDL commands to the replicate database, but does not update the tables in the table list when drop table or rename table DDL commands are encountered.
• replicate DDL with auto_extend_table_list – Sends DDL commands to the replicate database. For a table, if pdb_automark_tables is true, the table is automatically added to the table list when create table DDL commands are encountered.
• replicate DDL without auto_extend_table_list – Sends DDL commands to the replicate database, but does not add the tables in the table list when create table DDL commands are encountered.
• add tables in {(table_list) | files 'file_path'} – Adds tables to the replication path. You can either specify a list of tables or provide the table names in a file. After you add a table to the replication path, the data for that table starts replicating.
  Note: When adding or removing tables, you can specify only one file at a time and you must specify an absolute path for file_path.
• remove tables in {(table_list) | files 'file_path'} – Removes tables from the replication path.You can either specify a list of tables or provide the table names in a file.
• [in files ('file_path')] – A file that contains an include or exclude table list. You can specify only one file at a time and you must specify an absolute path for file_path.
  Note: The user who starts the primary Replication Server must have read permission to read the file.
  The table name format in a file and in a table list is the same. You can specify the table names in a table list in these formats:

  • ownername.tablename
  • tablename (the table name is stored as dbo.tablename)
  • *.tablename
  • ownername.*
  • '*x*y'.'a*b' (wildcard embedded in the string)

  Note: When create database replication definition is issued, the partial wildcard is expanded through all lists, including the table list and the exception list. The simple wildcard is expanded in the exception list before they are stored in the system table. You must specify values for user and password if your require any wildcard expansion.
  When you use an include or exclude table list, observe these guidelines:

  • The table name delimiter in the file must be a new line character.
  • Lines starting with # are ignored as comments.
  • Blanks before an owner name or table name are truncated.
  • The max length of an owner name is 30 characters.
• [user username password pass]– The user ID and password used to connect to the primary Adaptive Server database or Replication Agent and select from the primary table.
  If you use wildcard in a table name, you must specify values for user and password.

  Note: The user and password values are used once and are not stored in the RSSD.