May 6, 2006 at 3:28 am
Dear all,
I would like to know how to maintain the database log file size. I connect SQL2000 database with my application which is developed .Net language. Within one month, the log file size increase to 10 GB. I want to know the solution. is it concerned with pool size connection ?
Best Regards,
MK
May 6, 2006 at 3:42 am
The log file contains updates to the database and will increase automatically if allowed to by database settings and it is not truncated.
Depending on your maintenance plans you should regularly truncate the log following a successful database and/or log backup. Note that the log needs to be large enough to hold all transactions between backup/truncate. This is for Full recovery.
If the database is set to Simple then the log will be truncated at checkpoint but would still need to be large enough to hold all transactions between checkpoints.
To reduce the current size
Backup the database
Truncate the log
Shrink the Database
Be careful of the shrink as I cannot remember if it does both the data and log files
Far away is close at hand in the images of elsewhere.
Anon.
May 7, 2006 at 11:14 pm
Thanks for your reply. I know how to reduce the log file size but I want to know is why that log file size is increased quickly. When I use the application which is developed with vb programming, I have no problem. The database is the same. Why ?? I want to know the reason. If you know, pls explain me.
Best Regards,
MK
May 8, 2006 at 2:09 am
Check the log file
is it set to autogrow?
by how much?
what was it's original size when created?
is all the space in the log used?
If your log file is 10G then it was either created that size or has grown. If it grew then it is due to the updates and you will need to check the activity on the database. Don't forget not only are your application transactions logged but others as well, eg, those via EM, QA etc
Far away is close at hand in the images of elsewhere.
Anon.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply