I've been having problems with the database growing to 250mb on our site and shutting it down.  The support techs took a look and found that the Search tables were the culprit.  The normal size of the database runs less than 10mb.  I changed the Schedule entry from every 30 minutes to every 12 hours and that helped but it was still growing at what seems an inordinate rate.  Now I've disabled it to keep the site running.

Why should the Search tables take so much space?

William

I checked both the site and event logs when this problem first happened.  At that time the sitelog was rather large and contributing to the problem, so I cut it way back.  The event log was only 60 items or so.  Since then the search tables have filled up the database to it's limit of 250 mb several times, and I finally just shut down the scheduler event.

I made an error on the size of the database, it's more like 25 mb.  It's 6mb when RAR'ed.

It's a pretty small site.  It's only been up a few weeks, and it's pretty simple.  I don't understand why the search tables should grow to 200 mb - that's 4 times the size of the database without them.  The fact that they grow rather than get to a certain size and then stay that way would seem to indicate a bug in the indexing, such that older data is not being purged.  The site itself is nearly static, there's very little new content being added.  Shouldn't the size of the search tables also remain pretty much the same?

 I will reach out to others in the Core to see if they have ever seen this before.  The increments makes no sense in that it is not like it increments by 2x each time or something like that. 

Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation