Scott, Check out the DBCC commands, they are supposed to do what you want to do.
Although.... large log files can actually indicate non-committed transactions. Maybe a better question would be : Why is the system creating such large transaction log? You may actually have to export data from your db , destroy the original db and recreate then re-import. This is a horrible way to fix a huge log file, but it will work. Regards, Jared Clinton. NEC Business Solutions. -----Original Message----- From: Scott Weikert [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 11 September 2002 7:58 AM To: CF-Talk Subject: OT: Shrinking a SQL7 log file Hey gang - Any SQL7 gurus out there who know how to, resonably painlessly and safely, shrink a SQL7 database logfile from 83749234mb down to something reasonable? Any help (advice/instructions, or links to such) would be most appreciated. Replies off-list are fine. Thanks in advance, --Scott ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
