For better control our production log growth, I come up with the following tentative plan:
Set upper limit for log file size, say 10GB;
make backup log on a regular basis by a SQL Server job, say once per 7 or 3/4 days;
since there is guarantee that real log space never increases 5GB in 7days in our environment, and each backup log operation makes inactive virtual logs reusable.
This plan may work well for constraining our trans log within 10GB.
Comments, pros and cons, advice/suggestions?
BTW, any way to find out how many virtual log files are there, and active or inactive, and for SQL Server 2000 and 2008?
View Complete Post