|
|||||||||
|
|||||||||
|
|||||||||
 |
|||||||||
| |
||
|
|
|
|
|||||||||
|
|||||||||
|
|||||||||
|
|||||||||
| |
||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
ASP Free Forums Sponsor:
|
|
|
|
#1
July 26th, 2005, 03:49 AM
|
|||
|
|||
|
Extremely Log file grow
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 
|
|
#2
July 26th, 2005, 12:13 PM
|
||||
|
||||
|
Hi Kurt -
If you are not equipped to perform transaction log backups and restores, I strongly suggest you change the recovery mode of your database from "full" to "simple". To truncate your transaction log, do the following: Code:
sp_dboption 'database_name', 'trunc. log on chkpt.', 'on' DBCC SHRINKFILE (2, TRUNCATEONLY) sp_dboption 'database_name', 'trunc. log on chkpt.', 'off' The DBCC statement assumes that your log file's ID number is 2 (if it isn't, you've done some customization. Run a select * from sysfiles to find it's ID if you don't know). The DBCC should be run while using the problem database. The previous step will clear out the transaction log. To prevent the log from growing in the future, right-click on the database in enterprise manager, go to properties, select the options tab, and change the recovery model to simple.
|
|
| Viewing: ASP Free Forums > Database > Microsoft SQL Server > Extremely Log file grow |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
 |
|
|
|
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
