Can you compact a Microsoft Internal Database

Hello everyone, we are running SharePoint Services 3.0 and it is using Microsoft Internal Database and the size of some of the files have grown way out of control I think. Is there a way to compress them or clean them up?

Location of files....
C:|Windows\SysMSI\SSEE\MSSQL.2005\MSSQL\Data
Files that are in question...
CompanyDatabaseSharePoint.mdf (6,092,992 KB)
CompanyDatabaseSharePoint_log.LDF (60,736,000 KB)
SharePoint_Config_Random Letter/Numbers_log.LDF (19,352,192 KB)
WSS_Content_log.LDF (3,164,032 KB)
WS_Search_ServerName_log.LDF (2,160,960 KB)

As you can see those files are taking up almost 90 GB and our entire site is only about 5 GB total. Can anyone help me clean this up? Thank you in advance for your help!!
CCG3Sr Systems AdministratorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Justin SmithSr. System EngineerCommented:
First you must install SQL Manager Express to manage the databases (if you don't have it already).  It's a free download from Microsoft.

Once connected to your internal db instance, you should probably right click on all your SP databases - Properties, go to Options and change the recovery model to SIMPLE.  This will prevent you .ldf files from growing and growing.

Wait about 10 minutes after setting the recovery model.  Now, to shrink the ldf files down, right click CompanyDatabaseSharePoint and do New Query.

dbcc shrinkfile('companydatabasesharepoint_log',2000)

You will probably have to run the above a few times to get it shrunk all the way down.  The final size should be around 2 GB.  Now do the same for the config db.
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
Justin SmithSr. System EngineerCommented:
The reason why these ldf files get so big, is when the recovery is set to FULL, all database transactions are written to the log file (ldf) and remain there until the log is backed up.  If it is never backed up, it just grows and grows.

Either backing up the log file regularily (which truncates it), or setting the recovery to SIMPLE will prevent this in the future.  On internal db's, I usually just go to SIMPLE as you can't create management plans to regularily backup the logs (unless you know tsql).
0
CCG3Sr Systems AdministratorAuthor Commented:
Thanks for the replies! I have a test machine up now and I have restored SharePoint and I am trying to do what you are suggesting in a test environment first. I have installed SQL Server Management and I am trying to open those log files but I am getting sharing violation error. I have stopped the website from running and I changed the server type to SQL Server Type to SQL Server Compact Edition. But when I select one of those files I get the error.

Cannot connect to C:\Windows\SysMSI\SSEE\MSSQL.2005\MSSQL\Data\WSS_Content_log.LDF

There is a file sharing violation. A different process might be using the file.

Can someone tell me what I am doing wrong please? Thank you for your help!
0
The Five Tenets of the Most Secure Backup

Data loss can hit a business in any number of ways. In reality, companies should expect to lose data at some point. The challenge is having a plan to recover from such an event.

CCG3Sr Systems AdministratorAuthor Commented:
0
CCG3Sr Systems AdministratorAuthor Commented:
Hey everyone, I have done exactly what you all have suggested and my files are no smaller.

I installed SQL Manager Express.
I opened the databases, I went to Properties\Options, I changed the Recovery Mode from Full to Simple.
I waited 20 minutes, then ran some new quires and nothing has changed.

Does anyone have any other suggestions?
0
CCG3Sr Systems AdministratorAuthor Commented:
Never mind, again.

It was all me. I forgot to run the query. thank you for your help!!
0
Justin SmithSr. System EngineerCommented:
You've missed something or misstyped the query.
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.