Techniques for data retention

US10628387B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10628387-B2
Application numberUS-201414542353-A
CountryUS
Kind codeB2
Filing dateNov 14, 2014
Priority dateNov 15, 2013
Publication dateApr 21, 2020
Grant dateApr 21, 2020

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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.

First claim

Opening claim text (preview).

What is claimed is: 1. A method of managing data in a multitenant computing environment having a relational database and a non-relational database, the multitenant computing environment having multiple tenants where data for multiple tenants is stored in a single physical database object and tenant data is arranged so that data of one tenant is kept logically separate from that of other tenants so that one tenant does not have access to another tenant's data unless such data is expressly shared, the method comprising: identifying static data for a plurality of tenants in the multitenant computing environment to be maintained beyond a preselected threshold length of time with one or more server computing devices, wherein parameters to define the static data and the preselected threshold length of time are different for each of the plurality of tenants of the multitenant computing environment, wherein each tenant is a different organization comprising a plurality of users; copying the static data corresponding to the plurality of tenants from the relational database to the non-relational database; storing the static data in the non-relational database, wherein the static data in the non-relational database have the same logical separation for each tenant as the tenant data in the relational database; providing access to the static data from the non-relational database via a user interface that accesses both the relational database and the non-relational database; transforming a query received via the user interface in a relational database language to a scan for each row key range of multiple row key ranges thereby performing multiple parallel scans of the non-relational database to retrieve result data from the non-relational database corresponding to the query in the relational database language to perform a search of the static data stored in the non-relational database; and merging results of the multiple parallel scans of data in the non-relational database to present a combined result corresponding to the query received in the relational database language via the user interface. 2. The method of claim 1 , wherein the data comprises field history data. 3. The method of claim 1 , wherein a relational database environment and a non-relational database environment are part of the multitenant computing environment. 4. The method of claim 1 , wherein the copying the static data from the relational database to the non-relational database comprises: receiving a key prefix to identify the static data to be copied; splitting the static data to be copied into at least a first batch and a second batch; copying a first batch from the relational database to the non-relational database; automatically, in response to copying the first batch, enqueuing the second batch to be copied from the relational database to the non-relational database. 5. The method of claim 1 , wherein the identifying static data in the multitenant computing environment is performed in response to detection of one or more trigger conditions within the multitenant computing environment. 6. A system for managing data in a multitenant computing environment having a relational database and a non-relational database, the multitenant computing environment having multiple tenants where data for multiple tenants is stored in a single physical database object and tenant data is arranged so that data of one tenant is kept logically separate from that of other tenants so that one tenant does not have access to another tenant's data unless such data is expressly shared, the system comprising: at least one server computing device configured to provide services to one or more remote client computing devices; a database management environment configured to support services provided by the server computing device, the database management environment further configured to: identify static data for a plurality of tenants in the multitenant computing environment to be maintained beyond a preselected threshold length of time with one or more server computing devices, wherein parameters to define the static data and the preselected threshold length of time are different for each of the plurality of tenants of the multitenant computing environment, herein each tenant is a different organization comprising a plurality of users, copy the static data corresponding to the plurality of tenants from the relational database to the non-relational database, store the static data in the non-relational database, wherein the static data in the non-relational database have the same logical separation for each tenant as the tenant data in the relational database, provide access to the static data from the non-relational database via a user interface that accesses both the relational database and the non-relational database, transform a query received via the user interface in a relational database language to a scan for each row key range of multiple row key ranges thereby performing multiple parallel scans of the non-relational database to retrieve result data from the non-relational database corresponding to the query in the relational database language to perform a search of the static data stored in the non-relational database, and merge results of the multiple parallel scans of data in the non-relational database to present a combined result corresponding to the query received in the relational database language via the user interface. 7. The system of claim 6 , wherein the data comprises field history data. 8. The system of claim 6 , wherein a relational database environment and a non-relational database environment are part of the multitenant computing environment. 9. The system of claim 6 , wherein the copying the static data from the relational database to the non-relational database comprises: receiving a key prefix to identify the static data to be copied; splitting the static data to be copied into at least a first batch and a second batch; copying a first batch from the relational database to the non-relational database; automatically, in response to copying the first batch, enqueuing the second batch to be copied from the relational database to the non-relational database. 10. The system of claim 6 , wherein the identifying static data in the multitenant computing environment is performed in response to detection of one or more trigger conditions within the multitenant computing environment. 11. A non-transitory computer-readable medium having instructions stored thereon to manage data in a multitenant computing environment having a relational database and a non-relational database, the multitenant computing environment having multiple tenants where data for multiple tenants is stored in a single physical database object and tenant data is arranged so that data of one tenant is kept logically separate from that of other tenants so that one tenant does not have access to another tenant's data unless such data is expressly shared, the instructions, when executed by one or more processors, to: identify static data for a plurality of tenants in the multitenant computing environment to be maintained beyond a preselected threshold length of time with one or more server computing devices, wherein parameters to define the static data and the preselected threshold length of time are different for each of the plurality of tenants of the multitenant computing environment, wherein each tenant is a different organization comprising a plurality of users; copy the static data corresponding to the plurality of tenants from the relational database to the non-relational database; store the static data in the non-relational database, wherein the static data

Assignees

Inventors

Classifications

  • in federated or virtual databases · CPC title

  • Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title

  • G06F16/25Primary

    Integrating or interfacing systems involving database management systems · CPC title

  • Data format conversion from or to a database · CPC title

  • G06F16/284Primary

    Relational databases · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10628387B2 cover?
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…
Who is the assignee on this patent?
Salesforce Com Inc
What technology area does this patent fall under?
Primary CPC classification G06F16/25. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Apr 21 2020 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 2 related publications on this page (citations in our corpus or others sharing the same primary CPC).