TECHNIQUES FOR DATA RETENTION

• US 20150142736A1
• Filed: 11/14/2014
• Published: 05/21/2015
• 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
• Granted Patent: US 10,628,387 B2
• Time in Patent Office: Days
• US Class Current: 707/610
• 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 relational database environment and a non-relational database environment, the method comprising:

identifying data in the relational database environment that is static and to be maintained beyond a preselected threshold length of time with one or more server computing devices;

copying the data from the relational database;

storing the data the non-relational database; and

providing access to the data from the non-relational database via a user interface that accesses both the relational database and the non-relational database.

2. The method of claim 1 wherein the data comprises field history data.

3. The method of claim 1 wherein the relational database environment and the non-relational database environment are part of a multitenant environment.

4. The method of claim 1 wherein the copying the data from the relational database to the non-relational database comprises:

receiving a key prefix to identify the data to be copied;

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

copying a first batch of data from the relational database to the non-relational database;

automatically, in response to copying the first batch, enqueuing a second batch of data to be copied from the relational database to the non-relational database.

5. The method of claim 1 wherein identifying data in the relational database environment that is static and to be maintained beyond a preselected threshold length of time is performed in response to detection of one or more trigger conditions within the relational database environment.

6. A system for managing data in a relational database environment and a non-relational database environment, the system comprising:

at least one server computing device to provide services to one or more remote client computing devices;

a database management environment to support services provided by the server computing device, the database management environment to identify data in the relational database environment that is static and to be maintained beyond a preselected threshold length of time with one or more server computing devices, to copy the data from the relational database, to store the data the non-relational database, and to provide access to the data from the non-relational database via a user interface that accesses both the relational database and the non-relational database.

7. The system of claim 6 wherein the data comprises field history data.

8. The system of claim 6 wherein the relational database environment and the non-relational database environment are part of a multitenant environment.

9. The system of claim 6 wherein the copying the data from the relational database to the non-relational database comprises:

receiving a key prefix to identify the data to be copied;

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

copying a first batch of data from the relational database to the non-relational database;

automatically, in response to copying the first batch, enqueuing a second batch of data to be copied from the relational database to the non-relational database.

10. The system of claim 6 wherein identifying data in the relational database environment that is static and to be maintained beyond a preselected threshold length of time is performed in response to detection of one or more trigger conditions within the relational database environment.

11. A non-transitory computer-readable medium having instructions stored thereon to manage data in a relational database environment and a non-relational database environment, the instructions, when executed by one or more processors, to:

identify data in the relational database environment that is static and to be maintained beyond a preselected threshold length of time with one or more server computing devices;

copy the data from the relational database;

store the data the non-relational database;

provide access to the data from the non-relational database via a user interface that accesses both the relational database and the non-relational database.

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 the relational database environment and the non-relational database environment are part of a multitenant environment.

14. The non-transitory computer-readable medium of claim 11 wherein the copying the data from the relational database to the non-relational database comprises:

receiving a key prefix to identify the data to be copied;

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

copying a first batch of data from the relational database to the non-relational database;

automatically, in response to copying the first batch, enqueuing a second batch of data to be copied from the relational database to the non-relational database.

15. The non-transitory computer-readable medium of claim 11 wherein identifying data in the relational database environment that is static and to be maintained beyond a preselected threshold length of time is performed in response to detection of one or more trigger conditions within the relational database environment.

16. An apparatus for managing data in a relational database environment and a non-relational database environment, the method comprising:

means for identifying data in the relational database environment that is static and to be maintained beyond a preselected threshold length of time with one or more server computing devices;

means for copying the data from the relational database;

means for storing the data the non-relational database;

means for providing access to the data from the non-relational database via a user interface that accesses both the relational database and the non-relational database.

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

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

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

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

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

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

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

20. The apparatus of claim 16 wherein identifying data in the relational database environment that is static and to be maintained beyond a preselected threshold length of time is performed in response to detection of one or more trigger conditions within the relational database environment.