Posted by d.grabov on 11/22/06 13:53

I've been trying with:

BACKUP LOG dbname WITH TRUNCATE_ONLY
DBCC SHRINKFILE (dbname)

but the query cannot execute because of the mirroring


Erland Sommarskog wrote:

> (d.grabov@gmail.com) writes:
> > Thanks, the article makes some good points, however the log file is
> > over 30 times bigger than the database and 94% empty, hence the need to
> > shrink.
>
> Only if there is good reason to believe that it will not grow again. 94%
> empty is the current state of affairs, but if you regularly run a large
> operation, it will grow again.
>
> DBCC SHRINKFILE is what you use to shrink, but I don't know if there are
> any special considerations when mirroring is involved.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Re: float vs decimal
• Prev in forum: Re: Shrinking database log used for mirroring
• Thread view: Re: Shrinking database log used for mirroring

[Reply to this message]