LOG FILE SQL 2000 RESTRiCT GROWTH

[SeanB]

The log file is growing a great deal in our database is the best way to deal with this setup a scheduled Backup log file and then Shrink database then backup? Is there a way to restrict the log file from growing or is this a bad idea?

 

[tlbroadbent]

I would schedule regular backups, both full and transaction backups. I might even consider differential backups depending on the nature and frequency of the transactions. You can set the database to auto shrink or you can schedule a run to shrink it.

I don't believe it is a good idea to limit LOG growth. I believe it is important to monitor log growth.

Development of a backup strategy is critical. You would be wise to review backup topics in SQL BOL. I also recommend the following links for discussion of backup strategies.

http://www.swynk.com/friends/sjones/BackupStrategy.asp

http://www.swynk.com/friends/smirnov/backupsapp.asp

http://www.sqlmag.com/Articles/Index.cfm?ArticleID=9629

http://gethelp.devx.com/techtips/thesqlpro/10min/10min1100/10min1100.asp

http://gethelp.devx.com/techtips/thesqlpro/10min/10min1000-1.asp

Check these resources for information about shrinking the backup log.

Check the following resources.

Foxdev's FAQ183-345 in this forum.

Microsoft SQL 7 article

http://support.microsoft.com/support/kb/articles/Q256/6/50.ASP

Microsoft SQL 2000 articles

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da2_1uzr.asp

http://support.microsoft.com/support/kb/articles/Q272/3/18.ASP

At SWYNK.com

http://www.swynk.com/friends/krishnan/tranlogshrink.asp

Terry L. Broadbent
faq183-874 contains some tips and ideas for posting questions in these forums. Please review it and comment if you have time.
NOTE: Reference to the FAQ is part of my signature and is not directed at any individual.