Log shipping Fail over

Hi Paul,
To switch back roles from the new primary to old primary, why you need to
rename the server, use sp_dropserver, sp_addserver and restart the services?
Thanks for your help.
Pierre,
the reason is that you can't (easily) have 2 computers with the same NETBIOS
name on the same LAN.
Rgds,
Paul Ibison (SQL Server MVP)
|||Pierre,
Normally in log shipping role changes you do not change the server names.
Instead, the application must change its connection string to reference the
correct server.
Ron
Ron Talmage
SQL Server MVP
"Pierre Pilon" <Pierre Pilon@.discussions.microsoft.com> wrote in message
news:36E83F31-CEC9-4082-ABAF-96AC51DBA8BC@.microsoft.com...
> Hi Paul,
> To switch back roles from the new primary to old primary, why you need to
> rename the server, use sp_dropserver, sp_addserver and restart the
services?
> Thanks for your help.
|||Ron,
with respect, I think this depends on the setup
implemented. EG if there are loads of desktop
applications using DSNs which refer to the servername,
then changing each connection string may not be so
feasible. Also, if linked servers are being used to
reference the production server with 4-part qualified
names this will cause issues. Rescuing replication with
existing subscribers would be another issue, although
the 'standard' seems to be setting it up from scratch.
Master-slave jobs would probably be another difficulty.
Rgds,
Paul Ibison (SQL Server MVP)