In such cases I will: (a) work during downtime; (b) full backup of the database; (c) backup log myDatabase with truncate_only; (d) shrink the FILES as far as SQL allows.

After this procedure, often SQL will not allow us to shrink the Data file any further, but the Log File is often down to 1KB. That might help. When there's just a lot of data in the Database, it can only be shrunk so far and no further. But the Log file is a different question. Once we've done a backup, the data in the Log file (during downtime) is of no use to us. So I rarely let my Log files grow past 1GB anymore. IHTH.


-----Original Message-----
From: Dan Guzman
[mailto:mssqldba-ezmlmshield-x29018599.[Email address protected]
Sent: Tuesday, August 28, 2007 3:04 PM
To: LazyDBA Discussion
Subject: Shrink my log file!!

Ive tried full backups, then log backups, then full backups again. I've
tried Shrink files on the data and on the log file, nothing seems to
shrink this file. It's a 6 Meg database, with an 8 gig log file. I
would like to do this properly, so please, any suggests would be
helpful.

Dan

---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html




---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html



MS Sql Server LazyDBA home page