Re: Very large LDF

Hi,

This is because you are not performing the transaction log backup. The LDF
file will be cleared after the log backup.

How to shrink the existing LDF file:

1. Perform a Transaction log backup (BACKUP LOG - refer books online)
2. Use DBCC SHRINKFILE on trasnaction log file

Have a look into the below link;

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q272318

Note:

Check the Recovery model you are using for that database. If it is FULL and
your data is not critical then change the
Recovery model to SIMPLE. Simple recovery model will clear the Transaction
log after commiting.

If you need the recovery model as FULL then,

Schedule a Transaction log backup based on your data growth, This can be
used when point in time recovery.
This will ensure that ur log file wont grow much.


Thanks
Hari


"Atlas" <Atlas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:52FC44F4-7F78-4A97-AB79-1A157207C0A6@xxxxxxxxxxxxxxxx
Hello,

I have a database that has an extremely large LDF file. The DB is approx 1
GB and the LDF about 20 GB. Presumably the LDF file should not be this
large.
The database gets backed up using Veritas Backup Exec. Can someone tell me
what I should do to the database in order to reduce the LDF file as it is
taking up unnecessary space.
Is it just a mater of shrinking the database from Enterprise Manager or is
there allot more involved.
The DB is set to Full recovery model and gets backed up every night (using
Veritas Backup Exec)

Thanks



.

Relevant Pages

  • RE: What is the best practice to create Maintenance Plans
    ... > If master is damaged in some way, for example because of media failure, an ... > With the Simple Recovery model, the database can be recovered to the point ... > Full Recovery or Bulk-Logged Recovery model. ... > Transaction Log backup for master database is not allowed. ...
    (microsoft.public.sqlserver.security)
  • What is the best practice to create Maintenance Plans
    ... There is not a definitive answer to the question of which backup is better. ... the database can be recovered to the point ... Full Recovery or Bulk-Logged Recovery model. ... Transaction Log backup for master database is not allowed. ...
    (microsoft.public.sqlserver.security)
  • Re: transaction log
    ... It seems your Recovery model set to that database is "FULL". ... So we need to scdule a transaction log backup regularly (atleast hourly ...
    (microsoft.public.sqlserver.server)
  • Re:logfiles grow non-stop in SQL2000
    ... Looks like the recovery model for your database is FULL or BULK_LOGGED.Please change the recovery model for the database to ... If you do not have the 65 G to take a backup or if you do not want the transaction log backup. ... The logfiles for the most frequently-used databases grow non-stop. ...
    (microsoft.public.sqlserver.setup)
  • Re: Question about sql job, SQL 7 versus upgrade to SQL 2000
    ... Sounds like recovery model for 'sfa' database is set to "Simple". ... case transaction log backup is not possible. ...
    (microsoft.public.sqlserver.server)