Techniques for data retention

• US 10,628,387 B2
• Filed: 11/14/2014
• Issued: 04/21/2020
• Est. Priority Date: 11/15/2013
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Bruce, Jonathan Mark, Levine, Eli, Toens, Simon, Varley, Ian
• Primary Examiner(s): Hoang, Son T
• Application Number:
  US14/542,353
• Publication Number:
  US 20150142736A1
• Time in Patent Office: 1,985 Days
• Field of Search: None
• CPC Class Codes: G06F 16/18 File system types
• CPC Class Codes: G06F 16/20 of structured data, e.g. relational data
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/211 Schema design and management
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: G06F 16/217 Database tuning G06F16/2282 takes precedence; database performance monitoring G06F11/3409
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: G06F 16/245 Query processing
• CPC Class Codes: G06F 16/2471 Distributed queries
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06F 16/256 in federated or virtual databases
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 16/289 Object oriented databases

Abstract

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.

Claims

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 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.

12. The non-transitory computer-readable medium of claim 11, wherein the data comprises field history data.

13. The non-transitory computer-readable medium of claim 11, wherein a relational database environment and a non-relational database environment are part of the multitenant computing environment.

14. The non-transitory computer-readable medium of claim 11, 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.

15. The non-transitory computer-readable medium of claim 11, 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.

16. An apparatus 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 apparatus comprising:

means for 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;

means for copying the static data corresponding to the plurality of tenants from the relational database to the non-relational database;

means for 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;

means for 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;

means for 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

means for 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.

17. The apparatus of claim 16, wherein the data comprises field history data.

18. The apparatus of claim 16, wherein a relational database environment and a non-relational database environment are part of the multitenant computing environment.

19. The apparatus of claim 16, wherein the means for copying the static data from the relational database to the non-relational database comprises:

means for receiving a key prefix to identify the static data to be copied;

means for splitting the static data to be copied into at least a first batch and a second batch;

means for copying a first batch from the relational database to the non-relational database;

means for automatically, in response to copying the first batch, enqueuing the second batch to be copied from the relational database to the non-relational database.

20. The apparatus of claim 16, 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.