2

I am replicating a database using merge and had an issue where if the developers changed a procedure on the original database the change would not be pushed to the replicated database. Replicate schema changes is set to True.

Any guidance reason why the changes don't replicate? I did a snapshot before initiating replication. The developers claim it has worked in the past, though I am skeptical because it should not I believe.

Panagiotis Kanavos
  • 120,703
  • 13
  • 188
  • 236
Jersey
  • 151
  • 1
  • 7

1 Answers1

4

In merge replication,

Replicate schema changes set to TRUE means DDL changes of the merge tables are getting replicated ( e.g. ADD/REMOVE COLUMNS).

Other objects such as view,stored procedure,function etc changes can never be replicated using merge replication.

Ragesh
  • 740
  • 3
  • 9
  • How would you get a procedure to copy up to another database? – Jersey Jun 06 '16 at 14:26
  • 1
    Bad question. I am getting this error when trying to manually change the procedure now. The data definition language (DDL) command cannot be executed at the Subscriber. DDL commands can only be executed at the Publisher. In a republishing hierarchy, DDL commands can only be executed at the root Publisher, not at any of the republishing Subscribers. The schema change failed during execution of an internal replication procedure. For corrective action, see the other error messages that accompany this error message. The transaction ended in the trigger. The batch has been aborted. – Jersey Jun 06 '16 at 16:16