You might find these resources useful:
FileSize -How to stop the log file from growing
http://www.support.microsoft.com/?id=873235
FileSize -Log file filling up
http://www.support.microsoft.com/?id=110139
FileSize -Log File Grows too big
http://www.support.microsoft.com/?id=317375
FileSize -Log File issues
http://www.nigelrivett.net/TransactionLogFileGrows_1.html
FileSize -Shrinking Log in SQL Server 2000 with DBCC SHRINKFILE
http://www.support.microsoft.com/?id=272318
|||
This is a common problem in sql server. You need to understand few things in sql server like Recovery model, Transaction log physical architecture, How to keep the TL size under control and how to shrink the transaction log. If you are not taking Transaction log backup and you don't need to recover to a point in time ... then first thing you should do is change the recovery model to simple... If you want to have point in time recovery (STOPAT) then you should schedule the transaction log backup more frequently to keep the size within limit. Now since the log size is grwon over a period of time and if you need to reduce the size then follow these steps
(a)
backup log Somedatabase with truncate_only -- This statement will mark inactive part of log
(b) dbcc shrinkfile(DevGrantPlan_Log) -- This statement will release the marked inactive space to OS
(c) soon after this , the first step you must do is to backup the database. otherwise the backup chain is broken and you will not be able to use the TL backup for recovery
read the article mentioned by Arnie and it will give you more clear picture
Madhu
No comments:
Post a Comment