Why does replication add a column to replicated tables; will it be removed if the table isn published?
To track changes, merge replication and transactional replication with queued updating subscriptions must be able to uniquely identify every row in every published table. To accomplish this: • Merge replication adds the column rowguid to every table, unless the table already has a column of data type uniqueidentifier with the ROWGUIDCOL property set (in which case this column is used). If the table is dropped from the publication, the rowguid column is removed; if an existing column was used for tracking, the column is not removed. • If a transactional publication supports queued updating subscriptions, replication adds the column msrepl_tran_version to every table. If the table is dropped from the publication, the msrepl_tran_version column is not removed.
Related Questions
- Why does a column "Training" appear in the summary budget table A3.2, while no such column is provided in the A3.1 budget tables to be completed for each partner?
- Which DB2® Database catalog tables are used to produce a list of table column by table for all tables in a database?
- Why does replication add a column to replicated tables; will it be removed if the table isn published?
