February 11, 2002 at 1:59 am
Our backup stratergy is to do a full drive backup each night. Therefore we never use any of the log files from a database to restore with. My database log files have now grown to in some cases 3 times the size of the original database. How do I firstly clear down the log file and secondly is there a way of stopping the log file from being written? If not is it best if I write a stored procedure to clear this on a nightly basis?
February 11, 2002 at 4:24 am
Also after doing the items he listed for 2k if you are using, then do a shrink on the database and log file to force it back down. If you are using SQL 7 then you will find a sript on this site that can help wqith it as SQL 7 does not by default support. You can go here: http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=26 Forcibly Shrink the Transaction Log.
February 12, 2002 at 10:00 am
Is this a production site or dev site? If it's production and the db changes, why not get some log backups? Even in Dev, we've started some log backups. Once you understand how it works, It's nice to be able to recover as much as possible.
Steve Jones
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply