Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I support a SharePoint 2007 based public internet site that has a few performance problems. I just noticed that the hidden "Long Running Operation Status" list has nearly 10000 items in it. I can't imagine these are all still needed, I'm thinking I can delete all items where the status field is set to 'Successful'. However, I'm not sure what ramifications this may have.

Has anybody encountered this issue and/or done anything with this list?

share|improve this question
    
Why do you think cleaning up this list will help the performance problems? If this is a hidden list then SharePoint should have a mechanism to clean it up automatically after so many days. –  Alex Angas May 22 '11 at 5:39
    
Some of the performance problems are around the creation of new sub sites which I believe are long running jobs. I'm not proposing that this is the answer to all problems but it looks like an issue to me. I also would have thought that SharePoint should clean this list up. So the fact that is isn't is either a problem with my environment, or a general shortcoming. –  j.strugnell May 25 '11 at 16:11
add comment

2 Answers

So it turned out that the list gets purged weekly. I agree with Alex on areas to concentrate for performance issues. However we've done all that already and are clutching at straws to get better performance. Thanks.

share|improve this answer
add comment

This really falls into the "if it ain't broke, don't fix it" category. The "Long Running Operation Status" list is hidden and managed by SharePoint. As the list isn't explicitly exposed via the UI or through an API, you run the risk of making your farm unsupported by messing with it. Most of the problems around performance and lists with many items are caused by when those lists are queried, and that isn't happening here.

It would be better to focus on the specific performance issues you are experiencing or checking places where errors are logged such as the ULS or Windows Event Log rather than worrying about this list.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.