tag:blogger.com,1999:blog-8466427570171426704.post3782540335752333649..comments2023-09-28T05:10:14.156-04:00Comments on SQL Server: Shrinking the log file of secondary database in Log Shipping setupUnknownnoreply@blogger.comBlogger5125tag:blogger.com,1999:blog-8466427570171426704.post-79021361558367151922013-11-20T07:03:38.006-05:002013-11-20T07:03:38.006-05:00Thanks a bunch for your post.
Working fine for me...Thanks a bunch for your post.<br /><br />Working fine for me too.Chhavinath Mishrahttps://www.blogger.com/profile/01496708718906689250noreply@blogger.comtag:blogger.com,1999:blog-8466427570171426704.post-78124773203678839372013-10-24T03:09:45.657-04:002013-10-24T03:09:45.657-04:00You dont have to run BACKUP LOG WITH TRUNCATE_ONLY...You dont have to run BACKUP LOG WITH TRUNCATE_ONLY, just run the Logshipping backup Job a few times to inactivate the VLFs<br />We do this all the time on our Logshipping DBs... works like a charm<br />Great one Kaykay<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8466427570171426704.post-37227854774360394972013-07-22T23:26:41.335-04:002013-07-22T23:26:41.335-04:00yes your resolution is perfect. thanks you. very m...yes your resolution is perfect. thanks you. very much.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8466427570171426704.post-56100237195824281932012-06-25T10:42:45.493-04:002012-06-25T10:42:45.493-04:00I am sure if you try the following command it will...I am sure if you try the following command it will break the LSN and you will have to reinitialize the Log shipping setup.<br />BACKUP LOG WITH TRUNCATE_ONLY<br /><br />But this command has been deprecated and should never be used. But if you use the DBCC Shrinkfile command then the LSN does not break and LS works fine. I have tested this and hence the blogpost.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8466427570171426704.post-46080870200886314612012-06-25T00:15:14.511-04:002012-06-25T00:15:14.511-04:00Expert DBAs suggest that try to avoid use of trunc...Expert DBAs suggest that try to avoid use of truncate or shrink LDF file during log shipping enabled on the database because It will break the LSN (log sequence number) of transaction log backup. If you have done this then your log shipping will break. Once you shrink log file, you have to take full backup and then reset the log shipping.<br /><br />Regards,<br />Mark Willium<br />SQL Server Disaster Recovery Specialist<br />www(dot)stellarsqldatabaserecovery(dot)comMark Williumhttps://www.blogger.com/profile/14377582145723925411noreply@blogger.com