Re: Shrink Transaction Log

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Are you in full recovery? If so, are you performing full *and* log backups
regularly? What is your backup / recovery strategy? If you don't have one
(or don't need one), switch to simple recovery until you do. This will at
least minimize the persistent usage of the log, and will allow it to manage
itself through checkpoints. If you are not backing up properly then full
recovery isn't doing anything for you except making your logs explode. The
database is only as robust as you want to make it. If you say you want to
be in full recovery then you better take advantage of it.

Please read this in full:

http://tr.im/StopShrinking






On 5/29/09 10:39 AM, in article ed9mStG4JHA.4272@xxxxxxxxxxxxxxxxxxxx, "GMC
-LSND" <gcoleman@xxxxxxxxxxxxxxxxxxx> wrote:

SQL 2008

Just started using the above database and after a week, no one could get
into the database. A quick call to the creater of the software told me the
transaction logs in SQL 2008 needed to be shrunk. He walked me through it
really quick, but I found myself in the same situation a few days later.
Another call, another instruction to "shrink database".

I started reading a little and found that there are several ways to do this
and several reasons why or why not you would want to do this. I have found
that the database is unusable unless I do this.

My question is, is there a way to automate this so I don't have to manually
shrink it every couple of days? There has to be a way to do it as a database
this robust shouldn't hold you down to shrinking it every couple a days.

Thanks

gmc



.

Relevant Pages

  • Re: NTDS ISAM DataBase Corruption
    ... Did you tried the recover the corrupted Active Directory process that a gave ... This is brand new IBM Server. ... using symantec livestate recovery. ... Active Directory database is unavailable because it is damaged, ...
    (microsoft.public.windows.server.active_directory)
  • Re: SQL Database Purge
    ... Are you performing log backups regularly? ... set the database to simple recovery mode. ... > recovery model is set to FULL and the log file is nearly 66 GB. ...
    (microsoft.public.sqlserver.server)
  • Re: Crash recovery after shutdown immediate?
    ... database stated it wanted a recovery. ... it seems that a crash recovery occured. ... ARCH: Archiving is disabled ... After that, I did a backup, NOT a restore. ...
    (comp.databases.oracle.server)
  • RE: Eseutil and restored database - Jet database errors
    ... database repair (hard recovery). ... It approximately spends 1 hour for 6~8 GB database. ... Please refer to the "Method 3: Restore a Mailbox from Backup to a Recovery ...
    (microsoft.public.exchange.admin)
  • Re: Recover mailbox from old Backup...
    ... I never want to use these database files as a production mailstore. ... run the eseutil check, create a Recovery Store Group, ... I still have all the files from the old Exchange 2003 folder ... > I am running Exchange Server 2003 and the database files are from Exchange ...
    (microsoft.public.exchange.admin)