Replicating database schema changes in "daisy chain" situation
From: Tommy (Tommy_at_discussions.microsoft.com)
Date: 11/29/04
- Next message: JFB: "Still Error 18483"
- Previous message: Aviad Avi: "Replication"
- Next in thread: Vijay [MSFT]: "Re: Replicating database schema changes in "daisy chain" situation"
- Reply: Vijay [MSFT]: "Re: Replicating database schema changes in "daisy chain" situation"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 29 Nov 2004 12:37:03 -0800
We have a setup where SQL Server A servers as a Master database. SQL Server B
is installed in another country and replicates key master data from server A.
MSDE Instance C replicates with Server B to receive this master data as well
as merge data that is shared only between B and C. We recently needed to
change some column widths. I used the sprocs to add and drop columns to
recreate the columns with the new widths on server A. When we try to
replicate this to server B we get an error "The schema script 'exec
sp_repldropcolumn '[dbo].[<Table Name]', 'Column Name>', 1' could not be
propagated to the subscriber." It seems that since server B's tables are in
publications, the changes cannot be applied from server A. I tried running
the same SQL statements I ran on server A on server B to make the column
changes but it tells me that "Schema replication failed because database
<database name> on server <server> is not the original Publisher of table
<table name>." (this is returned from the sp_repladdcolumn call).
Any ideas on how to propogate the schema cahnges?
Tommy
- Next message: JFB: "Still Error 18483"
- Previous message: Aviad Avi: "Replication"
- Next in thread: Vijay [MSFT]: "Re: Replicating database schema changes in "daisy chain" situation"
- Reply: Vijay [MSFT]: "Re: Replicating database schema changes in "daisy chain" situation"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|