August 28, 2008 at 5:55 am
Hello,
I'm facing a situation that might be a bug.
I have 2 databases, one in brazil and the other in china. Each one replicates all the changes to the other by normal transaction replication.
It all works well, until I try to make an alter table. The create column itself replicates to the other, but the control procedures (sp_MSupd_xxx, sp_MSins_xxx) just show the new column on the replicated database !
I mean, if I add a column on the brazil database, the brazil procedures are not changed, only in china. So, what I always have to do is go to china database an copy the control procedures to brazil.
This is at least akward.
Some body experiancing that ?
Thanks !
Rodrigo
August 28, 2008 at 11:46 am
Rodrigo Moreira (8/28/2008)
Hello,I'm facing a situation that might be a bug.
I have 2 databases, one in brazil and the other in china. Each one replicates all the changes to the other by normal transaction replication.
It all works well, until I try to make an alter table. The create column itself replicates to the other, but the control procedures (sp_MSupd_xxx, sp_MSins_xxx) just show the new column on the replicated database !
I mean, if I add a column on the brazil database, the brazil procedures are not changed, only in china. So, what I always have to do is go to china database an copy the control procedures to brazil.
This is at least akward.
Some body experiancing that ?
Thanks !
Rodrigo
In normal transactional replication, sp_MSupd_xxx, sp_MSins_xxx, sp_MSdel_xxx procedures are called only on the replica, not on the primary. So the DDL change is applied on the replica sever only.
* Noel
August 28, 2008 at 1:02 pm
You are right.
My case is not typical and I guess that I will have to copy the procedures for each change.
Thanks !
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply