i have a server that runs sql 2005 and the logfile has grown ridiculously high, which means the logfile is now 80gb.
i have a dev server with sql 2005 on which the logfile is 10gb.
i want to shrink and i was told to simply run a SHRINK and that should work. i try on the dev server first, and when i run the ''basic shrink'' to simply remove empty space, it takes it down to 8gb, but i want to have the logfile smaller.
i then run shrink again and i see an option to specify the logsize, so i specify the log to 3gb, but it does not shrink it down.
what should i do ?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
to give more context, here is what the shrink file says :
TYPE : LOG
FILEGROUP NA
FILENAME : GPDBLOG.LDF
LOCATION ...
CURRENTLY ALLOCATED SPACE : 8265
AVAILABLE FREE SPACE : 7741.43 (93%)
SHRINK ACTION :
RELEASE UNUSED SPACE (i ran this and it reduced from 10-8 gb)
REORGANIZE : SIZE : 3000mb ( i ran this and it did not do anything
EMTPY AND MOVE TO ANOTHER FILE (i ran this and it did not do anything either)
hope it helps a bit
is the database recovery mode SIMPLE ?
YES -> solution:
* if you cannot shrink the logfile, you simply have to ensure you run some transactions, and retry the DBCC SHRINKFILE.
NO ->
do you run regulary full AND transaction log backup on that databse
YES -> the log file should not have grown that big, unless you have REALLY alot of transactions, and the transaction log backup interval is too large
solition :
* reduce the transcation log backup intervals, and ensure that transactions are not too big.
NO ->
that is the problem. implement transaction log backups, and then refer to the above
In case you overlooked my comment, please check it out to understand how it works.
an additional word of explanation:
the sql server transaction log file is in short a circular buffer, and when the current pointer is located at the end of the file, then shrinking of the log won't do anything.
transaction log backup (not the full backup alone) + doing some transactions will get that pointer moved to the beginning of the file, then another log backup and then the shrink will work,.
Business Accounts
Answer for Membership
by: PFrogPosted on 2007-04-20 at 05:25:03ID: 18945702
you need to back up the database first - shrink will only remove logs that have been backed up