Teiid does not have built-in change data capture facilities that can scrape logs, install triggers, etc. to capture change events - that is up to the system installer. Teiid is not source of the record, so it has no idea when the data in source is changed, unless all the updates are done through the Teiid to the underlying system. If you can generate change data capture event based on the data in source, then you can use eventing facilities in Teiid to issue cache refreshes. If using result set caching the Teiid instance can be notified via the EventDistributor bean - there is no system procedure hook at this time for that call. That will appropriately flush resultset and other cache entries that were built off of the specified tables (we do not yet go down to the row/column granularity, whole cache entry gets flushed). The EventDistributor or updateMatView system procedures can be used to update single rows of materialized views based upon data changes, which allows for those caches to be incrementally updated. Look for EventDistributor interface in the "api" module, you can look up this bean using JNDI in the same VM as Teiid. Once you obtain the instance of this bean, you can call the methods on this interface to when appropriate data source specific events come in. HTH. Ramesh.. On 04/11/2012 10:04 AM, Reeves, Russell wrote: