Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
klegrand
Starting Member
29 Posts |
 Posted - 2005-07-26 : 02:37:29
|
| My database log file is extremely growing. In the properties of the database, the transaction log setup was in the beginning restricted to a max. size. The 60Gb disk is in 1 day completely full when I set it to unrestricted file growth.Why is this growing so fast ? The amount of inserted records is +/- 100/hour.I've also a job running that's cleans up the log file.Can anyone help me with this ? Thx,Kurt |
|
|
franco
Constraint Violating Yak Guru
255 Posts |
Posted - 2005-07-26 : 05:10:52
|
| Do you take backup of your databases and transaction logs?From BOL:When SQL Server finishes backing up the transaction log, it automatically truncates the inactive portion of the transaction log. This inactive portion contains completed transactions and so is no longer used during the recovery process. Conversely, the active portion of the transaction log contains transactions that are still running and have not yet completed. SQL Server reuses this truncated, inactive space in the transaction log instead of allowing the transaction log to continue to grow and use more space. Although the transaction log may be truncated manually, it is strongly recommended that you do not do this, as it breaks the log backup chain. Until a full database backup is created, the database is not protected from media failure. Use manual log truncation only in very special circumstances, and create a full database backup as soon as practical.HTHFranco |
 |
|
|
|
|
|
Extremely Log file grow