WSS 3.0 Config Database (SharePoint_Config) is 50GB!

I have WSS 3.0 set up on my server using the default Windows Database that is setup with WSS 3.0.  I have connected to it using MSSQL Server Manager Express and found that the size of the SharePoint_Config database is 50GB! Further investigation shows that this is the transaction log, and this is the INITIAL size it was set to!  Doing a transaction log backup will not shrink it below the initial size, so I'm stuck with this massive file on a server when the content is only 2 sites and they contain about 7 GB worth of data (content) as shown by the size of the SharePoint content database (not shown).  The problem here is that I am running out of disk space and since this is taking up more than 35% of my available space, I would like to make it MUCH smaller.

My question is two-fold.

1.  Is the a standard size for this database?  Seems awfully large to me.
2.  Can I reduce the minimum size of this file without adverse effects?  If so, what size?

Thanks in advance for your help.
test.JPG
LVL 1
mdiehly64Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brad HoweDevOps ManagerCommented:
You can shrink the log without losing any content.  This grows for transactions beacuse the DB is in FULL Recovery -- which is good.

To reduce this you can do the following below.

I would suggest creating a maintance plan to execute these tasks once a week as well.

-------------
USE SharePoint_Config;
GO
-- Truncate the log by changing the database recovery model to SIMPLE.
ALTER DATABASE SharePoint_Config
SET RECOVERY SIMPLE;
GO
-- Shrink the truncated log file to 1 MB.
DBCC SHRINKFILE SharePoint_Config_Log, 1);
GO
-- Reset the database recovery model.
ALTER DATABASE SharePoint_Config
SET RECOVERY FULL;
GO
------------------------

Cheers,
Hades666
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mdiehly64Author Commented:
Awesome.  Worked beautifully.

Since I'm using the Express version of SQL, I don't think I can set up a maintenance plan.  If this is not the case, please write back and let me know where to find it.  There is nothing under tools.  I wonder if I could run a transact-SQL script and plant it somewhere?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.