August 5, 2002 at 7:43 am
For some strange reason the transactionlog from one of the databases does not grow (what it did before). Does anyone know how to solve this issue (removing the transactionlog and making a new one? how?)
Edited by - normanshark! on 08/07/2002 06:30:22 AM
August 5, 2002 at 8:13 am
When you say the transaction log does not grow, are you getting to the point where the transaction log is full and not auto-growing or is it that you've allocated X MB of space and it hasn't grown past that yet?
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
August 6, 2002 at 12:19 am
A while back to Transactionlog was set to auto grow and it had grown to more than 1.6GB and the server was running out of space. Shrinking for some reason didn't do the job. I searched on the internet and I found a script that dumped all the information in the transactionlog. The size now is about 1.5 MB and filled with .9 MB of data. Settings set to autogrow (but this time set a size limit of 1 GB). When I have a look (do that on a regular bases) of the database size and occupied (allocated)space there is no change what so ever in the transactionlog.
All the other databases I have running don't have this problem. It's only the one!
Any idea?
(MS SQL 7, sp3)
August 6, 2002 at 5:09 am
Do you have it set to truncate on checkpoint? The log will grow if you have a transaction that exceeds the ability of SQL store it in the log at its current size or if you have not backed up the transaction log and there is not enough space to store the transaction. Nothing says the log has to grow if properly sized or you use truncate on checkpoint (really both, since even in truncate mode it could grow with a large transaction).
Andy
August 7, 2002 at 6:30 am
Thanks Andy!
it was indeed set to truncate on checkpoint. I removed this and now everything is fine!
Dave
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply