Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Problems Shrinking Log File Expand / Collapse
Author
Message
Posted Thursday, November 8, 2012 4:24 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 3:44 AM
Points: 146, Visits: 282
Ah apologies, yes you're right, you would have to set RECOVERY to SIMPLE and then run the shrink commands in SQL 2008.
Forgot that this was a discountinued command in 2008
Post #1382403
Posted Thursday, November 8, 2012 4:29 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, August 1, 2013 10:17 AM
Points: 323, Visits: 984
McSQL (11/8/2012)
Ah apologies, yes you're right, you would have to set RECOVERY to SIMPLE and then run the shrink commands in SQL 2008.
Forgot that this was a discountinued command in 2008



be aware about this . this can break LSN chain in log file


-----------------------------------------------------------------------------
संकेत कोकणे
Post #1382404
Posted Thursday, November 8, 2012 4:31 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 6:52 AM
Points: 5,131, Visits: 4,918
sanket kokane (11/8/2012)
McSQL (11/8/2012)
Ah apologies, yes you're right, you would have to set RECOVERY to SIMPLE and then run the shrink commands in SQL 2008.
Forgot that this was a discountinued command in 2008



be aware about this . this can break LSN chain in log file


So does TRUNCATE_ONLY, should only ever use it if you dont care about recovery and if you dont care about recovery need to step back and decide if you actually need to be in the full or bulk logged recovery model.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1382405
Posted Thursday, November 8, 2012 4:36 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 3:44 AM
Points: 146, Visits: 282
Yeah they both do, and I only suggested it on the basis that the log file was at 50GB (from a standard 4GB), and therefore log shipping and log backups were unlikely to be taken, at least with any regularity.

The better option is to set up maintenance routines on your logs to prevent them getting to that size, but in the event you're not maintaining logs or are out of space, then it is an option to consider.
Post #1382411
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse