10 pts.
 How to control SQL Server transaction log growing to a maximum size
Transaction log in SQL Server getting completely growed to maximum size frequently even when it is being backed-up and shrinked.. Please provide early and feasible solution.. What is the possible cause for the growth of transaction log to that extent.. and how to avoid it...

Software/Hardware used:
ASKED: January 24, 2008  1:54 PM
UPDATED: February 22, 2008  6:02 AM

Answer Wiki:
It's probably being caused by maintenance plans rebuilding indexes and updating statistics. There isn't any way to stop it from happening. You need to plan for this. You may need to increase the size of the log drive.
Last Wiki Answer Submitted:  February 22, 2008  6:01 am  by  Sap.sree   70 pts.
All Answer Wiki Contributors:  Sap.sree   70 pts. , GregMM   60 pts. , Denny Cherry   64,520 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


 

Check out my SQL Server blog “SQL Server with Mr Denny” for more SQL Server information.

 64,520 pts.

 

I pulled the other answers out of the answer as they don’t appear to apply.

Have you been able to resolve your problem?

 64,520 pts.