sql server replication: Alexander,
a few questions to clarify things:
is this a restore of a publishing database, or a scripted publication from
another server run on this server?
what type of replication is involved?
does it currently work (changes successfully propagated to the subscriber,
assuming trans or merge)?
what schema change do you need to do?
Regards,
Paul Ibison

Alexander,
when you "add new column using dialog from Enterprise Manager" is this the
publication properties, filter columns tab (using sp_repladdcolumn)?
If not then try using this dialog box. If it is, then the easiest way to
repair the situation is to synchronize the data, remove the publication (and
run sp_removedbreplication on all databases if they no longer have
publications or subscribers) then create the publication from fresh on the
publisher and initialize with the nosync option. This sounds like a lot of
work but is relatively straightforward.
HTH,
Paul Ibison

Alexander ,
in sysmerge articles there is a publisherid. This ID needs to have a
corresponding record in sysmergepublications. However, in
sysmergepublications, the 'publisher' column needs to match the servername,
which it doesn't in your case as you have restored to another servername. It
might be possible to update the 'publisher' column, although I'd advise
against it and suggest recreating. The BCP of the data is the timeconsuming
step on initialization, and in your case this is not required.
HTH,
Paul Ibison

Hi!
I've got the following error, while trying to change schema on published DB:

21260 16 Schema replication failed because database '%s' on server
'%s' is not the original Publisher of table '%s'.


Please tell me what I have to do, to be able to change schema?
Thanks.

Best regards,
Alexander Kachalkov.

Thanks for quick response Paul!

[quoted text, click to view]

Yes, this is a restore of a publishing database.

[quoted text, click to view]

Snapshot and Merge.


[quoted text, click to view]

Yes, it is.

[quoted text, click to view]

I need to rename one column and add relationship to another table.
As I know there is only one way to do this.
Add new column with wanted name and drop the old one.
When I try to add new column using dialog from Enterprise Manager.
I've got the message 21260 that schema was generated on another server :(
At present there is 4 subscribers.


[quoted text, click to view]

[quoted text, click to view]

Exactly.

[quoted text, click to view]

This sounds very bad, if I have 100 subscribers..
Ok, I will try.

Tell me why this had happened with DB?
As I know when backup and restore replication DB all replication data is
removed?
Some technical details would be usefull.

[quoted text, click to view]