Re: transaction log blow up

From: Janet (anonymous_at_discussions.microsoft.com)
Date: 08/08/04 

Date: Sun, 8 Aug 2004 06:01:00 -0700

I definitely would like to maintain transaction log
backups, so you're correct it is set to FULL.
Uri, do you have any idea how a log could blow up to 30
GB? There's no way we had a transaction any where near
that size.

>-----Original Message-----
>Janet
>If don't carry about the data you can set recovery model
to SIMPLE . I
>presume you are in a FULL recovery model
>
>"Janet" <anonymous@discussions.microsoft.com> wrote in
message
>news:20e401c47d07$3c0dd8c0$a501280a@phx.gbl...
>> Hi, I have a database which takes up 2GB for the .mdf
>> file. It's on a brand new server that has over 30GB of
>> free space for the disk where the log file resides. The
>> other day, the log file expanded to fill all 30GB of
the
>> disk. I truncated the log and shrunk the log file. I
also
>> increased the transaction log backup so occur every 1
>> hour instead of every 4 hours which is what I had it
set
>> to. I also put a limit 2GB limit on the log file.
>>
>> My question/concern is why did the log file get so
large
>> in the first place? What are usually some of the
reasons
>> why a log for such a small database increase to the
full
>> capacity of the disk?
>>
>> Thanks,
>> Janet
>
>
>.
>

Relevant Pages

  • Re: Log file...
    ... Are you backing up the log file? ... backups of the log - my first guess would be that you ... Another option is if the transaction log is not part of your ... shrinking, growing of the log consumes resources. ...
    (microsoft.public.sqlserver.server)
  • RE: Log Shipping and Full Backup Frequency. Advice?
    ... The transaction log is different; it is a recording of database actions. ... And, if you restore from any of these, you only get that state. ... This is not the case with the transaction log or its backups. ...
    (microsoft.public.sqlserver.server)
  • Re: Restore Database w/Large Transaction Log File
    ... If I am reading you correctly, the backup has already been trasmitted to the ... AGAIN, just like the other respondents have told you: shrink the log file, ... Shrinking a database transaction log file that has that has been pre-gone to 200 GB in size, will not save any disk space on the restore. ...
    (microsoft.public.sqlserver.server)
  • Re: Still dont understand log backups
    ... The transaction log, whether or not it is one or many files, is a serial, ... until the end of the physical log file is reached. ... backup is executed, the active "virtual" logs are backed up, but the ... Using BULK LOGGED, does the online log file contain EVERY transaction for all time -- given that I don't truncate it manually? ...
    (microsoft.public.sqlserver.server)
  • Re: optimum log file size
    ... Fixing of Transaction log file based up on the amount of bulk transaction ... CUrrent log growth will be because of FULL recovery mode. ... If you do not require a point in time recovery or if your database ...
    (microsoft.public.sqlserver.clients)