Event-driven updating of the BDC index.

A typical business scenario for using business data search would be one where users need to access data on new customers provided by the company’s Siebel implementation. Though the index will provide a snapshot of the customers that existed at the time of the last crawl, new customers might have been entered since that time that might be of high interest. Unfortunately, no built-in event raising mechanism exists to signal the index that new records have been entered and an incremental crawl is needed. One workaround to this issue, and one, moreover that accords with the way crawler is intended to work, is to create an IDEnumerator method that could detect changed records and kick off an incremental crawl. From a performance viewpoint, it would be undesirable to have a crawl initiated whenever there was a new record, but this impact could be minimized if only changed records were indexed at convenient intervals.