Posted by NiTiN on 07/25/06 07:19

To get a secondary up and running, I've disabled the SQL Server Agent
jobs, restored the last transaction log (with recovery) and I've got a
working database. I was just wondering what I'd do if the last
transaction log has already been applied with norecovery.

Later, when the former primary is functional, I'll just restore from a
full backup, overwriting the existing database, and then will setup
transaction log shipping on the new primary which will automatically
get the new logs restored.

I didn't execute any stored procedures, though... it was GUI all the
way for me.

N.I.T.I.N.


NiTiN wrote:

> I've got SQL Server 2005 Ent Ed 9.0.1399 and want to change my
> secondary Log Shipping server into a primary. I've tried locating the
> sp_change_secondary_role, but can't seem to find it. Has it been
> replaced with another stored procedure? If so, which are the procedures
> to run?
>
> On SQL Server 2000, the following were the steps listed:
> 1. Transfer logins
> 2. Run sp_change_primary_role
> 3. Run sp_change_secondary_role
> 4. Run sp_change_monitor_role (this exists in SQL Server 2005)
> 5. Run sp_resolve_logins
>
> 3 & 5 are what I'd expect to perform if the primary isn't available.
>
> N.I.T.I.N.

[Back to original message]