We help IT Professionals succeed at work.

clean up Sharepoint

Hello Experts!

After several years using a Sharepoint WebApplication , we began to have a large number of little problems.

In analysis, we found some "debris" in the Sharepoint database.

I Believe that will be necessary to "clean up" directly in the Sharepoint database.

I wonder to know if there is a tool to facilitate this cleaning, and what are the best practices for direct transactions in the Sharepoint database (I know that it is not recommended).

Thank you!
Comment
Watch Question

Commented:
Are you sites very large site collections?
Cause I believe it is easier and safer to backup and restore the sites in new databases rather then modifying the database.

Author

Commented:
Hi,

Approximately 20 site collections, with 20 subsites each.
The database have 10GB.

For security reasons we will.
- Replicate the Database in current testing environments.
- Test the action manually remove items from Sharepoint Database.

My post is aimed at:
- To learn the best practices for handling data directly at the base of sharepoint.
- To learn tools to facilitate this action.
- Learn how to prevent the accumulation of dirt in sharepoint.


Can you help me?

Thx
Commented:
What is the actual "debris"? You don't say what you found which makes it difficult to make a recommendation.

The answer to your second question you already know, there are no best practices because it is totally unsupported (not just not recommended). If you hose it up you are on your own as far as support.
Commented:
It is a very good idea to replicate database in testing environment.
But, instead of cleaning it, i would rather try moving the site collections to another database. This would be supported and you could even contact MS for support in doing this move (unless you already modified the database that made it "dirty")
Beside, I don't think you will find anywhere a guide on how to clean the database.

Take a small site collection, back it up using stsadm -o backup and then restore in the new created content database. See if that comes out correctly.

Like Steve_NJ suggested, would be good to post some information on the actual faults, maybe someone already encountered something similar and may provide a better input than a general idea.
Senior Software Developer
Top Expert 2009
Commented:
If you touch the database directly you void all support from Microsoft and violate the EULA agreement.

@irinuc, @Steve_NJ it is in violation of the EE Membership Agreement to help anyone violate another agreement.

@br_ms: The only solution is to create all or portions of the farm.  Accessing the database directly is very dangerous and will likely make things worse.
Commented:
That's why I'm inerested in what the debris is so we can make other recommedations.
Ted BouskillSenior Software Developer
Top Expert 2009
Commented:
I wanted to make it very clear that we are treading dangerous ground.

The only command I know of to make database repairs is the following:
http://technet.microsoft.com/en-us/library/cc263282%28office.12%29.aspx

Author

Commented:
TThx