Hi,
I have inherited a log shipping environment configured with no monitor server. I am getting the error explained in the article below, however there is no monitor server. What is the best practice on making this threshold change when there is no monitor server?
To resolve the problem, correct the@threshold_alert parameter value for the secondary database by executing the following statement on the monitor server.
use mastergosp_change_log_shipping_secondary_database @secondary_database = 'dbname', @threshold_alert = 14421
Thanks.
Frank.
Frank Garcia