February 17, 2010 at 7:29 am
Can anyone tell me as how to change out of sync threshold value in a log shipping environment. I am getting 14421 error and I have found that the out of sync threshold value is set to 12 min. The copy job itself takes around 10 min to complete. I found the out-of-sync value from log_shipping_secondaries table.
-Lucky
February 18, 2010 at 5:52 am
Can anyone tell me how to change this setting please
February 18, 2010 at 6:27 am
I don't have logshipping on SQL2008 but presuming it has not changed from 2005 its set on the restore transaction log tab under 'secondary server instances and databases' in the log shipping wizard
(right click database - properties)
---------------------------------------------------------------------
February 18, 2010 at 6:59 am
Books Online (hit F1) to the rescue!
sp_change_log_shipping_primary_database
sp_change_log_shipping_secondary_database
See the @threshold_alert and threshold_alert_enabled parameters in particular.
Paul
February 18, 2010 at 8:02 am
I don't have a resolution for your immediate problem but I have a suggestion for the future. You might execute the process more often to generate smaller dumps which should take less time to copy..
CEWII
February 19, 2010 at 6:05 am
Paul,
Can't we make the threshold change using GUI? Do I need to run sp_change_log_shipping_primary_database and sp_change_log_shipping_secondary_database?
February 19, 2010 at 6:33 am
luckysql.kinda (2/19/2010)
Can't we make the threshold change using GUI? Do I need to run sp_change_log_shipping_primary_database and sp_change_log_shipping_secondary_database?
You can. The details are in the same main section of Books Online.
February 19, 2010 at 7:12 am
unless the gui has really changed in SQL2008 instructions on how in my original post.
---------------------------------------------------------------------
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply