Re: out of control T-Log? NEED HELP PLEASE...

From: randyvol (anonymous_at_discussions.microsoft.com)
Date: 03/22/04 

Date: Mon, 22 Mar 2004 13:41:08 -0800

     Sorry -
I neglected to state that I have also done T-log backups... at least I think I have. Maybe you can tell me...
Here's the script for the particular DB in question...

<snip>
BACKUP LOG WHALEYAPPS TO
DISK = 'D:\EMSQLT_BKPS\WHALEYAPPS_LOG.trn'
WITH INIT, STATS = 25
<end snip>

     ----- Tibor Karaszi wrote: -----
     
     Full backup doesn't empty the log backup. And shrink won't work either as
     the haven't emptied the log file. Either do regular transaction log backups
     or set the database to simple recovery model. As for shrinking of the log
     files, there are a few useful links in below article:
     
     http://www.karaszi.com/sqlserver/info_dont_shrink.asp
     
     --
     Tibor Karaszi, SQL Server MVP
     http://www.karaszi.com/sqlserver/default.asp
     
     
     "randyvol" <randy.volters@whaleyfoodservice.com> wrote in message
     news:08ED6880-34CD-4A06-A18B-26DE8DA5AA27@microsoft.com...
> Hello -
>> I have a problem with a T-Log file that just seems to keep growing no
     matter what I do...
>> Here are the file sizes:
> MDF 563,648 KB
> LDF 3,244,544 KB !!!
>> I have done full backups on this database
> I have done DBCC shrinkdatabase
> I have done DBCC shrinkfile (<LDF filename>, TRUNCATEONLY) (where <LDF
     filename> is the name of the logfile)
>> Nothing seems to affect the size of this file.
>> I even, in desperation, thought that perhaps there was an open transaction
     in the log file, so I ran DBCC OpenTran ('<DBNAME>') (where DBNAME is the
     name of the database) I got back no active open transactions.
>> There is just no way that I can see that this database (either MDF or LDF
     file should be that big.
>> Does anyone have any advise ??? Thanks in advance.
>> Randyvol
     
     
     

Relevant Pages

  • Re: Database Size, Database Corruption, Message Store & Storage Group
    ... More careful monitoring of the server. ... Each extra storage group also requires more memory at startup, ... Also it is important to know if there was actually database corruption. ... In terms of backups, you should look at "how" you are performing backups. ...
    (microsoft.public.exchange.admin)
  • Re: Advice Requested : Disaster Recovery with 2 Drives (No Raid) with SQL Server 2008
    ... so we need frequent copies of the database for testing, ... Andrew J. Kelly SQL MVP ... But by placing the backups on the same drive as the data or logs you risk loosing data if one of the drives crashes since you will loose backups and either the log or data files. ...
    (microsoft.public.sqlserver.programming)
  • 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: Pervasive SQL 8.6
    ... and backups are done by copying the files off to tape - ... you'll want to have lots of memory on the server -- ... drives for the database files. ... set up your SAN with a configuration of 80% memory set ...
    (comp.databases.btrieve)
  • Re: Maintenance Recomendations -Compact?
    ... recs" you actually mean Maintenance Requirements, ... your database is still monolithic; ... That frequent Compact and Repair ... So, in addition to the above, take frequent backups of your ...
    (microsoft.public.access.gettingstarted)