Reputation: 1
Renamed a production instance during a move to virtual. The aftermath was that our replication broke. The replication subscriber and publisher both were removed and the jobs disabled - but every day the publisher and distributor try to still read the logs.
Has anyone experienced this before? Can you point me in the direction of what I need to do to fix this?
Upvotes: 0
Views: 315
Reputation: 3755
You cannot rename an instance that is involved in replication. It will break replication. You must drop and recreate replication after a rename.
Upvotes: 1