SQL Server Performance Forum – Threads Archive
SQL Server Log shipping – structure changes?
I’ve just started delving into this.<br /><br />I’ve got a wizard do a VERY simple log ship for a test database (VERY SIMPLE – 0 tables [<img src=’/community/emoticons/emotion-2.gif’ alt=’
CREATE TABLE is a logged operation and if it is completed on the primary server then the next set of log shipping process should affect the same on the secondary server during the restore. For further clarity I will have a test of the process and come back to you. (and you too.. enjoy the rest of cricket test matches with WI [8D]) Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS†with no rights for the sake of knowledge sharing.
Thank’s Satya … I will enjoy the cricket, especially the test cricket – it’s been a while since we could smile about test cricket, especially with the mauling England gave us, not to mention the India tour [:/] … I have done a create table, and at this point in time, it doesn’t appear to have been shipped across – I’ve also inserted data…. no joy, even though LS alleges it has running with no problems for the: Log Shipping Alert Job – Restore
Log Shipping copy for (local).TestLogShip_logshipping
Log Shipping Restore for (local).TestLogShip_logshipping
jobs… The Log Shipping Alert Job – Backup job has been complaining about 14420 errors – but that was since the creation – I susepct I did something stupid with the creation of the 1st maintenance plan, regarding the out of synch threshold – I don’t believe it has any effect on what I am doing (per above) I’ve create a second job, with a second test db – I’ll see if that has better luck (since I re-checked the out of synch thresholds for that one). BTW – it would "seem" that I might be able to use sp_update_log_shipping_plan to change the out of synch switch? Panic, Chaos, Disorder … my work here is done –unknown
As part of log shipping, alert messages 14220 and 14221 are generated to track backup and restoration activity. The alert messages are generated depending on the value of Backup Alert threshold and Out of Sync Alert threshold respectively. My test here is successful and I can see the table creation on the secondary server without any issues. I would suggest to recheck the maintenance plans created by the wizard (I never trust them) and better to go with pre-defined scripts to the installation. (On the lighter side, cricket is good game…I love it and plays too. I feel winning and losing is a part of it… it only matters in the world cup for me) Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS†with no rights for the sake of knowledge sharing.
Hmm – the wizard (I also mis-trust them, unless they are part of (a) the fantasy book I am reading, (b) the computer game I am playing [<img src=’/community/emoticons/emotion-1.gif’ alt=’


I mean to say use the MS scripts that are defined in the Log shipping process as explained in thishttp://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship1.mspx article for reference. I tend to say better not to depend on the maintenance plans, rather create own log shipping jobs by referring to the created jobs. (Yeah, expecting a warm summer this time… good to play more) Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS†with no rights for the sake of knowledge sharing.
Found my mistake – errors in log shipping UNC directory – Transaction Lgo backups weren’t being found and copied. Panic, Chaos, Disorder … my work here is done –unknown
]]>