October 2, 2008 at 12:03 am
I CONFIGURED LOGSHIPPING,BUT THE LOG FILE SIZE IS INCRESING,WHY?
WHAT IS THE REASON BEHIND THAT?
KINDLY HELP ME...
REGARDS
PHANI
October 2, 2008 at 12:54 am
The log file grows too large because this is the way the application is running the back-end transactions; unless you can optimise tsql, it seems you have to do the maths for your database size, re capacity planning.
What can be done:
- increase the log shipping latency until a point where you do not cause a network problem - 10 or 15min?
- make sure you log file autogrowth is set to a fixed value, not percentage
- monitor, monitor, monitor how often your log file grows: dbcc sqlperf( logspace) then resize again
October 2, 2008 at 5:57 am
Do you have replication on the DB?
Is the log shipping running? (are the backups of the log working?
Please don't shout (type in all caps).
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply