[dba-SQLServer]SQL LOG File is Huge! 10GB - Help

To shrink your logs and DB, first run a full backup, then for the log 
file you can run the following command, substituting of course the log 
name and the number of megs/gigs you actually want for the size.

DBCC SHRINKFILE (YOURDBLOGName, 10)



Eric Barro wrote:

> Julie,
> 
> You need to go through the following steps to reduce the size of your transaction log files
> 
> 1. Backup the transaction log.
> 2. Shrink the transaction log - you can do this just for the transaction log.
> 3. Keep going through the shrinking transaction log process until it's down to a few hundred megs.
> 4. When the logs are of a manageable size make sure that you put limits on the size of the logs.
> 5. Schedule a job that backs up the transaction logs after several hours.
> 6. Schedule a job that shrinks the database at night on a nightly basis.
> 
> ---
> Eric Barro
> Senior Systems Analyst
> Advanced Field Services
> (208) 772-7060
> http://www.afsweb.com 
> 
> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com
> [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Julie
> Reardon-Taylor
> Sent: Wednesday, October 08, 2003 6:35 AM
> To: AccessD at databaseadvisors.com; dba-SQLServer at databaseadvisors.com
> Subject: [dba-SQLServer]SQL LOG File is Huge! 10GB - Help
> 
> 
> 
> Hi Group,
> 
> All of a sudden, my BEDB.dbf file has grown huge.  The file itself and the 
> log file are at 10GB.  I tried shrinking the database, and received a 
> message saying that it was successful, however, the files are still the same 
> size.  I'm receiving an event log error ID 17052 that states that there is 
> no more room in the log file.  How can I resolve this problem?  It is 
> causing problems on the server because the files are taking up so much 
> space.  It is error 9002, severity 17.
> 
> 
> Julie Reardon-Taylor
> PRO-SOFT OF NY, INC.
> www.pro-soft.net
> 
> _________________________________________________________________


-- 
-Francisco