What if the eventcache table is too large?

Method 1:

Web Application General settings

 

Method 2:

Stsadm-O setproperty-URL <URL>-PN change-log-expiration-enabled-PV true

Stsadm-O setproperty-URL <URL>-PN change-log-retention-period-PV <days to keep change log>

Stsadm-O setproperty-URL <URL>-PN job-change-log-expiration-PV <schedule, 'Every 2 minutes 'or 'daily at'>

 

Method 3:

Stsadm.exe-O addcontentdb-clearchangelog

This method will cause immediate loss of alert emails, and the next incremental crawl for the content dB will become full crawl, so as to ensure that the items in the index exist in the DB.

 

2011-10-06-Update

I remember a customer once said that his eventcache table was growing very fast, and thousands of records were updated every minute. after investigation, we found that it was not because of incorrect settings, but because the customer set the job interval to 1 minute during user profile sync.

This is because the user profile sync debugging result is displayed immediately.

Because the setting of this interval is not changed back to the default value, profile sync leads to a large number of eventcache records.

Set the time of the timer job back to solve the problem.

Stsadm-O sync-synctiming H: 1

 

Reference

======================

Addcontentdb: stsadm operation (Office Sharepoint Server)

Http://technet.microsoft.com/en-us/library/cc263422 (office.12). aspx

Complete reference of all stsadm operations (with parameters) in Moss 2007 SP1

Http://blogs.technet.com/ B /josebda/archive/2008/03/15/complete-reference-of-all-stsadm-operations-with-parameters-in-moss-2007-sp1.aspx

Timer job: stsadm properties (Windows SharePoint Services)

Http://technet.microsoft.com/en-us/library/cc424953 (office.12). aspx