We a have a data under SQL 2005 which has a large log file that's 90% empty.
I'm trying to shrink it by right-clicking the database and selecting Shrink,
as I do with other databases. However, this specific database doesn't
shrink without any error messages. The only difference is that it is a
mirrored database.
Mirrored DBs can have log file growth, sue to network outages between the
primary and the mirror. I'd think twice before shrinking it. You may need
the space again. Also, check out:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp

Signature
Tom
----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
We a have a data under SQL 2005 which has a large log file that's 90% empty.
I'm trying to shrink it by right-clicking the database and selecting Shrink,
as I do with other databases. However, this specific database doesn't
shrink without any error messages. The only difference is that it is a
mirrored database.