Is there an easy way to take apart replication when a server has been
renamed. The sever in question was a subscriber to one publication and the
publisher of another. Is there an easy way to drop the relvant subscriptions
publications now that this server has been renamed. As I presume sql does not
just adapt to the new name?
I concurr with Paul. Replication is sensitive to the publisher name, so
renaming the publisher breaks the agents.
You are best to (as Paul suggests) script out and rebuild your publications
and subscriptions.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:1d5101c4d7c0$4c921030$a501280a@.phx.gbl...[vbcol=seagreen]
>I would script out the replication settings then disable
> replication on the server. Make sure that SQL Server has
> been reconfigured:
> Use Master
> go
> Select @.@.Servername
> This should return your current server name but if it
> returns NULL then try:
> Use Master
> go
> Sp_DropServer 'OldName'
> GO
> Use Master
> go
> Sp_Addserver 'NewName', 'local'
> GO
> Stop and Start SQL Services
> Then edit your scripts accordingly with the new
> servername, reenable replication on the server and run
> the scripts.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
> server has been
> publication and the
> relvant subscriptions
> presume sql does not
Wednesday, March 21, 2012
Help after the server was renamed before replication was taken dow
Labels:
apart,
beenrenamed,
database,
dow,
microsoft,
mysql,
oracle,
publication,
renamed,
replication,
server,
sever,
sql,
subscriber
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment