Salesforce Com, Inc.

William Dumaresq

Mikhail Chainani

Xiaodan Wang

Gary J Baker

Varun Jobanputra

Venkat Chandrasekaran

Utsavi Benani

Jia Chen

Vijay Devadhar

Technology for tracking changes to a database and providing the changes to a subscribing computing device. In an illustrative implementation, a method may involve subscribing a computing device to changes of a portion of a multi-tenant database and accessing a plurality of change events stored in a log of the multi-tenant database in parallel. The method may further involve storing the plurality of change events in a persistent data store separate from the multi-tenant database and processing the plurality of change events to create an ordered set of change events. The ordered set of change events may then be provided to the computing device that subscribed to the changes.

Parallel processing of disjoint change streams into a single stream

Methods and systems for providing a rewind of table data in a data management system include: storing a table having table data that defines a plurality of rows and a plurality of columns that define a plurality of cells; capturing change data associated with changes to at least one of the plurality of rows, the plurality of columns, and the plurality of cells; associating the change data with a transaction having a transaction identifier; storing the transaction and the change data in a change bus; retrieving the change data from the change bus based on a rewind request; performing a rewind of a subset of the changes by performing a reverse operation of the change data relating to the subset of changes and according to a reverse operation order; and outputting a clone of the table based on the rewind of the changes of the table.

Undo based logical rewind in a multi-tenant system

A system may identify gap events in a change detection stream. When changes in data are transmitted to a downstream system, the system may identify intermittent portions of the transmission where data is missing (e.g., a gap event). In some examples, a gap event may be caused by system maintenance or one or more system errors. After identifying the gap event, the system may bridge the gap event using metadata associated with the gap event. The associated metadata may be transmitted (e.g., via a gap event identification message) to the downstream system, which may prevent the downstream system from experiencing computational inefficiencies due to the gap event.

Processing gap events in a change detection management system

Growing community of inventors

San Francisco, CA, United States of America

William Dumaresq