Log Shipping shrink the secondary server.
in [Server Configuration]
|
Prev: OLE DB provider "SQLNCLI10" for linked server "XXXXXX" returned message"The stored procedure required to complete this operation could not be found onthe server. Please contact your system administrator.".
Next: Create Account
From: hiteshmirchandani on 29 Dec 2009 23:36 I have configured a log shipping setup, unfortunately I did not shrink the log file before taking the backup on the primary server. Now I realized that the log file on the secondary server is really big. The DB has been configure to be in standby & redonly mode... Can I shrink the secondary databases log file .. & what would the best method be for it Thanks
From: Andrew J. Kelly on 30 Dec 2009 10:54
If the log file needed to be that big on the primary it will also need to be that big on the secondary as well as they will have the same exact transactions applied. I haven't tried it but I see no reason why you cant shrink it but not sure that you should. What are you trying to accomplish by shrinking it? -- Andrew J. Kelly SQL MVP Solid Quality Mentors <hiteshmirchandani(a)gmail.com> wrote in message news:f405c340-cebf-4de7-8a0d-fff55011ba30(a)o28g2000yqh.googlegroups.com... > I have configured a log shipping setup, unfortunately I did not shrink > the log file before taking the backup on the primary server. > > Now I realized that the log file on the secondary server is really > big. The DB has been configure to be in standby & redonly mode... Can > I shrink the secondary databases log file .. > > & what would the best method be for it > > > Thanks > |