Change Log Shipping Monitor Server - SQL 2000

The below content is reused from http://www.sqlservercentral.com/Forums/Topic289235-9-1.aspx

The steps were executed by me and it works.

The steps are described as below
1. Script the "Log Shipping Alert - Backup" and "Log Shipping Alert -
Restore" jobs from the current monitor server
2. Run the following query on current monitor server and save the output -
select maintenance_plan_id from msdb.dbo.log_shipping_primaries
select secondary_plan_id from msdb.dbo.log_shipping_secondaries
3. Execute the scripts created in Step 1 on the new monitor server (in MSDB)
4. Execute the following stored proc on the new monitor server -
sp_add_log_shipping_primary
@primary_server_name = '' ,
@primary_database_name = ''
,@maintenance_plan_id = 'in Step 2>'
,@backup_threshold = freq of backup job>
,@threshold_alert = '14420'
,@threshold_alert_enabled = 1
,@planned_outage_start_time = 0
,@planned_outage_end_time = 0
,@planned_outage_weekday_mask = 0


5. Execute the following select statement to get the Primary_ID in the new monitor server-
select primary_id from msdb.dbo.log_shipping_primaries where
primary_server_name =
'' and primary_database_name = 'name>'
6. Execute the following stored procedure on the new monitor server with the appropriate Secondary Server, and Second db_name and plan_id derived from the select stmt of the current monitor server, for each of the seconday the same needs to be repeated -
sp_add_log_shipping_secondary @primary_id =
, @secondary_server_name = ''
, @secondary_database_name = ''
, @secondary_plan_id = ''
, @copy_enabled = 1
, @load_enabled = 1
, @out_of_sync_threshold = times the freq of copy/restore jobs>
, @threshold_alert = '14421'
, @threshold_alert_enabled = 1
, @planned_outage_start_time = 0
, @planned_outage_end_time = 0
, @planned_outage_weekday_mask = 0
7. Execute the following statement on the Primary and secondary servers to
get the current monitor login information. Verify that you have 1 for logon
type before proceeding with step
8. If you do not have this field set to 1,
then for the time being we will change the authentication mode to NT and
then we can change this later on once the monitor is completely migrated -
select * from msdb.dbo.log_shipping_monitor
go
8. Execute the following command on both Primary and all secondary servers
to change the monitor information -
delete from msdb.dbo.log_shipping_monitor
go
sp_define_log_shipping_monitor '', 1, NULL, 1
go
9. This should complete the migration. Test that the monitor server icon
thing appears under Management tree (Enterprise Manager). When you click
this Log Shipping Monitor, there should be the new pair that you just
added. Once the jobs are working successfully the last copied/loaded file
field will be updated to reflect the changes.


--------------------------------------------------------------------------------

Scott Duncan