Salesforce Com, Inc.

Salesforce, Inc.

Ian Varley

Eli Levine

Jonathan Bruce

Simon Toens

Scott Hansma

Paul Burstein

Lars Hofhansl

Systems and techniques for managing data in a relational database environment and a non-relational database environment. Data in the relational database environment that is static and to be maintained beyond a preselected threshold length of time is identified. The data is copied from the relational database and stored in the data the non-relational database. Access to the data is provided from the non-relational database via a user interface that accesses both the relational database and the non-relational database.

Techniques for data retention

An application for creating an editing a knowledge graph for document retrieval and exploration. The application may create a data structure, arranged as a directed acyclic graph (DAG), based on user input indicative of categories within a taxonomy and documents within an information repository. The DAG may have a top-level node, interior nodes, and leaf nodes. Interior nodes correspond to taxonomic classifications and point to other interior nodes or leaf nodes. Leaf nodes have corresponding interior nodes and include links to one or more documents in the information repository. The application permits editing of nodes, but does so in a way that preserves links to the arrangement of nodes prior to the editing. The application also permits traversal of nodes of the data structure via a user interface in which a representation of a given node includes an indication of one or more possible paths for reaching the given node.

Knowledge graph for information retrieval and exploration

A multi-master replication system is disclosed. The multi-master replication system allows a large set of peer instances to collaboratively replicate data to each other. According to an example, a change detection thread running on a first server associated with a first instance of multiple instances of a replicated database monitors for changes to any of multiple records within one or more shared tables of the replicated database. Responsive to detection of a change to a record, an item is stored by the change detection thread onto a queue containing information regarding the change. Groups of changes are packaged into multiple chunks, in which each chunk (i) corresponds to a discrete unit of progress for both change detection and transport; (ii) is associated with multiple changed records; (iii) contains metadata about the multiple changed records; and (iv) does not contain data from the one or more shared tables.

Multi-master data replication in a distributed multi-tenant system

A database may store a plurality of database revisions corresponding to a time period, including a current version and one or more backup versions of a data object. After a threshold time has passed, the database may identify a plurality of time intervals within the time period and identify, for each of the plurality of time intervals, at most one database revision corresponding to the time interval. The database may delete, for each of the plurality of time intervals, all of the database revisions except for the identified at most one database revision. The database may periodically repeat this process to reduce the granularity of backup data over time.

Reducing granularity of backup data over time

A multi-master replication system is disclosed. The multi-master replication system allows a large set of peer instances to collaboratively replicate data to each other.

Growing community of inventors

Austin, TX, United States of America

Ian Varley