Runtime detector for data corruptions
Assigneesalesforce.com, inc.
InventorRohitashva Mathur
Life of this patent
Estimating the term…
Loading patent…
Assigneesalesforce.com, inc.
InventorRohitashva Mathur
Estimating the term…
In a multitenant data platform architecture, one or more supporting data tables are used to efficiently retrieve data responsive to data retrieval requests. Programmatic code markers associated with contextual data about a data transaction thread are identified. The contextual data is examined using the one or more programmatic code markers invoked by the database in the data transaction thread at runtime. Based on the contextual data returning an indication of a data corruption in one or more supporting data structures, an action associated with the data transaction thread is performed. A log of data corruptions and corresponding call stack trace data may be generated. The data transaction thread may be allowed to continue to execute statements that modify data tables, or the data transaction thread may be terminated.
A computer-implemented method, comprising:
One or more non-transitory computer readable media, storing one or more sequences of instructions, which when executed by one or more processors cause performance of:
A system, comprising:
Dependencies are inferred from the claim text.
From the US filing history. Foreign family members aren’t listed.
Drawings are temporarily unavailable. Open the PDF at USPTO
Design, administration or maintenance of databases: improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or…
Indexing; Data structures therefor; Storage structures: tablespace storage structures; Management thereof
Computing and data processing
About 12 years 8 months of term left · ends 9 Jul 2039 (estimated)
The present invention relates generally to cloud-based data retrieval, and in particular, to a runtime detector for identifying data corruptions in custom indexes and other data structures that support data retrieval processes.
A large-scale cloud-based computer system may include multiple datacenters at various geographic locations to maintain millions of sets of application data for millions of organizations as well as provide millions of sets of application services such as those for customer relationship management (CRM), secured data access, online transaction processing, mobile apps, etc., to respective users and/or customers of these organizations.
Architecturally, the large-scale cloud-based computer system may rely on a multitenant architecture that employs standard objects while using custom indexes and other data structures that are used to store and retrieve customer data. However, over time, data corruptions may prevent a tenant from accessing correct data.
The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:
FIG. 1A illustrates an example overall data corruption runtime detection framework; FIG. 1B and FIG. 1C illustrate an example configuration for data objects in a multitenant data platform architecture;
FIG. 2 illustrates an example high-level block diagram, including an example corruption detecting platform;
In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, that the present invention may be practiced without these specific details. In other instances, well-known structures and devices are not described in exhaustive detail, in order to avoid unnecessarily occluding, obscuring, or obfuscating the present invention.
Example embodiments are described herein according to the following outline: 1.0. General Overview 2.0. Functional Overview 3.0. Example Embodiments 4.0 Implementation Mechanism—Hardware Overview 5.0. Extensions and Alternatives
This overview presents a basic description of some aspects of an embodiment of the present invention. It should be noted that this overview is not an extensive or exhaustive summary of aspects of the embodiment. Moreover, it should be noted that this overview is not intended to be understood as identifying any particularly significant aspects or elements of the embodiment, nor as delineating any scope of the embodiment in particular, nor the invention in general. This overview merely presents some concepts that relate to the example embodiment in a condensed and simplified format, and should be understood as merely a conceptual prelude to a more detailed description of example embodiments that follows below.