November 17, 2008 at 9:30 am
Alvin Ramard (11/17/2008)
Is there more "stuff" save to Sharepoint than should be? Are there multiple copies that could be delete? Can anything be archived or deleted, etc, etc, etc, .................
The thing with ss is it is as good or as inteligent as you program it to be. For exaple I am designed an event handler for ours so that when a u ser attempts to check in some 'stuff' it analysis the file type and file size and then based on 'business' and 'management' need, transparantly puts the data either in the db or a $ ntfs share (hidden from users) of course the meta is kept but that will stop the database from going crazy.
You can also put limits on you ApplicationPools but from the sound of it that would be like locking the gate after all you horses had done a runner!
My 2-cents, you need ss consultancy and sql training. Sorry mate 😎
Adam Zacks-------------------------------------------Be Nice, Or Leave
November 18, 2008 at 11:02 am
If you want to stop this database from growing, then you might want to consider turning off the search index feature. I assume that you either set this up or it was setup by deafult. Either way, you can just disable the scheduled crawl or stop the search servcie entirely. However, be aware that your users will not be able to search content. This might not be your desired result.
Anotehr option, more realistic, is to narrow your search options and make sure you are only crawling relavant data. Perhaps your users only need particular data search...then scope this out in your crawls.
Beware, SharePoint databases can become very large very fast....pre-planning is key but a difficult art.
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply