Shareplex does not support theuse of the copy table for a table that is involved in a vertically partitioned replication.
The workaround is:
1.Drop the target table.
2.Use the force option to copy, namely copy owner.table2 force
3.Once the copy is complete, you can drop any columns in the target table that you do not wish to be there.
As the above message from the sp_ctrl implies, the use of force option on a table in replication may cause out-of-sync conditions.
The Shareplex Reference Guide has the following section that mentions that the copy or append is not supported for Vertically Partitioned replication and one may have to use the above workaround if using copy on such tables:
What the copy/append command does not support
.
.
Tables in replication that are horizontally or vertically partitioned.
.
.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center