Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Sharepoint content source problem

  Asked By: Nirmal    Date: Mar 17    Category: Sharepoint    Views: 1258

I had some large content source indexes in Sharepoint, but I've since
deleted those indexes. The problem is sps.edb hasn't shrunk back to a
reasonable size. It's still sitting at 1.7 gigs. Is there a utility
I can run to force it to purge?

Share: 

 

4 Answers Found

 
Answer #1    Answered By: Siobhan Waller     Answered On: Mar 17

I don't recall the exact syntax, but you'll want to look for eseutil
usage statements for defragging the files. I believe that gets rid of
the extra deleted space.

btw, an online defrag should occur every night already. It's on by
default. You can look in the event view for events like this:

Event Type: Information
Event Source: ESE98
Event Category: Online Defragmentation
Event ID: 700
Date: 5/2/2003
Time: 3:30:11 AM
User: N/A
Description:
Information Store (3924) Online defragmentation is beginning a full pass
on database [drive]:\pathto\wss.mdb'.

and then it finishes:

Event Type: Information
Event Source: ESE98
Event Category: Online Defragmentation
Event ID: 701
Date: 5/2/2003
Time: 3:39:46 AM
User: N/A
Description:
Information Store (3924) Online defragmentation has completed a full
pass on database '[drive]:\pathto\wss.mdb'.

My database is about 6GB and it takes 9 mins. Sometimes it shaves a
whole GB from the total size  of my backups. I'm assuming that my
content is changing rapidly enough for it to expire when the indexes  are
refreshed.

 
Answer #2    Answered By: Lorenzo Steele     Answered On: Mar 17

I have been looking at this question also and immediatly thought of the
ESE defrag - check KB 285040. -
http://support.microsoft.com/default.aspx?scid=kb;[LN];Q285040
But Beau is looking at SPS.edb which contains the indexes. The article
does not speak of using it on this file, only the wss.mdb file. Does
this work on the sps.edb file?

 
Answer #3    Answered By: Divakar Naik     Answered On: Mar 17

We've had the same issues, and we've run  the utility directly on sps.edb
without any problems.

 
Answer #4    Answered By: Marcus Davis     Answered On: Mar 17

I'm unsure, and I've removed my test sps  server and replaced it with a
test SPS v2.0 beta server. I did a quick google search but found
nothing but a french page that just happened to mention eseutil and
sps.edb together.

Maybe a backup and a restore will result in a smaller file, but I doubt
it.

Another option might be to backup, delete the file, re-run full indexes,
and testing. Do this on a test server.

 
Didn't find what you were looking for? Find more on Sharepoint content source problem Or get search suggestion and latest updates.




Tagged: