By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,412 Members | 1,630 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,412 IT Pros & Developers. It's quick & easy.

SQL server log file is not shrinked

P: n/a

I have MS SQL server 2000 with MOM server. I was able to shrink the
database file, but when i try to shrink the log file i fail. I use
"shrink database" wizard and try to reduce the log file from 640 MB to
32 MB and i select this number in "shrink database to __" and wait. I
got a success message box but the old size remains.

Any ideas?

Jul 23 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
(Mo*****@gmail.com) writes:
I have MS SQL server 2000 with MOM server. I was able to shrink the
database file, but when i try to shrink the log file i fail. I use
"shrink database" wizard and try to reduce the log file from 640 MB to
32 MB and i select this number in "shrink database to __" and wait. I
got a success message box but the old size remains.


In this particular case, I would say: leave it alone. 640 MB is a fairly
small log file. Risk is only that if you succeed to shrink it that it
will increase in size again, and that will only take resources.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
Jul 23 '05 #2

P: n/a
Erland

Not being a SQL expert, I have experienced the same following upgrading
from SQL7. The way I solved the probem was to backup the Transaction
Log file seperately and then either the log file shrinks or you can
shrink the the db.

Hope this helps

Dave

Erland Sommarskog wrote:
(Mo*****@gmail.com) writes:
I have MS SQL server 2000 with MOM server. I was able to shrink the
database file, but when i try to shrink the log file i fail. I use
"shrink database" wizard and try to reduce the log file from 640 MB to 32 MB and i select this number in "shrink database to __" and wait. I got a success message box but the old size remains.
In this particular case, I would say: leave it alone. 640 MB is a

fairly small log file. Risk is only that if you succeed to shrink it that it
will increase in size again, and that will only take resources.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp


Jul 23 '05 #3

P: n/a
see
http://www.mindsdoor.net/SQLAdmin/Tr...leGrows_1.html

In your case as tis is a mom database you could probably set the
recovery model to simple. Depends a bit on what you are using it for.

Nigel Rivett
www.nigelrivett.net

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Jul 23 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.