US20150142844A1 - Scalable objects for use in an on-demand services environment - Google Patents
Scalable objects for use in an on-demand services environment Download PDFInfo
- Publication number
- US20150142844A1 US20150142844A1 US14/542,338 US201414542338A US2015142844A1 US 20150142844 A1 US20150142844 A1 US 20150142844A1 US 201414542338 A US201414542338 A US 201414542338A US 2015142844 A1 US2015142844 A1 US 2015142844A1
- Authority
- US
- United States
- Prior art keywords
- relational database
- database
- data
- environment
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G06F17/30607—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2471—Distributed queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- H04L67/42—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/211—Schema design and management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/214—Database migration support
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/217—Database tuning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/256—Integrating or interfacing systems involving database management systems in federated or virtual databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/289—Object oriented databases
Definitions
- provisional utility application No. 61/904,822 entitled “SCALABLE OBJECTS,” filed on Nov. 15, 2013, and having attorney docket No. 1362PROV
- provisional utility application No. 61/904,826 entitled “MULTI-TENANCY FOR A NOSQL DATABASE,” filed Nov. 15, 2013, and having attorney docket No. 1363PROV
- provisional utility application No. 61/905,439 entitled “BIG OBJECTS,” filed Nov. 18, 2013, and having attorney docket No. 1364PROV
- provisional utility application No. 61/905,457 entitled “ORCHESTRATION BETWEEN TWO MULTI-TENANT DATABASES,” filed Nov.
- Embodiments relate to database management. More specifically, embodiments relate to providing services from both a relational database environment and a non-relational database environment.
- FIG. 1 is a block diagram of one embodiment of an architecture that may provide big objects as described herein.
- FIG. 2 is an interaction diagram of one embodiment of a technique for querying a non-relational (NoSQL) database using relational database (SQL) commands.
- NoSQL non-relational
- SQL relational database
- FIG. 3 illustrates a block diagram of an environment where an on-demand database service might be used.
- FIG. 4 illustrates a block diagram of an environment where an on-demand database service might be provided.
- a relational database may be needed for some data and/or may have been the basis for data when the services started.
- Data that does not require the relational database can be, for example, data that does not change over time, thus not requiring the ACID (Atomicity, Consistency, Isolation, Durability) properties of the relational database.
- ACID Automatic Identification, Consistency, Isolation, Durability
- a new object type (sometimes referred to herein as a “big” object) is provide that can “unhook” customers/tenants/organizations from these constraints when it is desirable and/or appropriate to do so.
- a system provides declarative and programmatic ways to construct and use these big objects.
- the system can operate to create custom objects within the bounds of a relational database, such as an Oracle® database, and replumbing it to a higher scale.
- Custom objects are custom database tables that allow a user to store information unique to their organization.
- the system creates objects through the Salesforce (SFDC) metadata application programming interface (API) and, yet, data goes to a non-relational (e.g., NoSQL) database, such as HBase instead.
- NoSQL database can, in some instances, hold more information that is addressable from the SFDC platform.
- all the standard features of Salesforce work with both the relational database and the non-relational database.
- a customer/client/tenant will have a large volume of data to be stored, the data is historical in nature (can be considered immutable) and access to the data can be controlled by simple accessibility rules, and native platform sharing is not required.
- Use of the big objects as described herein can be accomplished with different types of data as well.
- the techniques herein allow customers/tenants/organizations to be unleashed from data limits that could interfere with application effectiveness.
- the Big Object feature set asserts a differentiating primitive—it allows customers/tenants/organizations to think at scale from the inception of their data, but also that these objects are conceived and used independent of the functional expectations and feature set of traditional base platform and custom objects.
- the big objects utilize frameworks such as the the Metadata API from salesforce to push data to a NoSQL database such as HBase where vast amounts of data can quickly be analyzed, yet the system still provides the same functionality as a SQL server, in terms of allowing queries and other features to be implemented on the data.
- frameworks such as the the Metadata API from salesforce to push data to a NoSQL database such as HBase where vast amounts of data can quickly be analyzed, yet the system still provides the same functionality as a SQL server, in terms of allowing queries and other features to be implemented on the data.
- the following behavior is assumed when utilizing big objects.
- the data in one implementation, is immutable—it cannot change its current form. Yet, the data has full API and SOQL access from the platform. Data immutability can force a consciousness on users to take a more prescriptive look on the data they have on the platform, which objects contain data that needs to change on a frequent basis, and which data does not need to change.
- data mutations utilize a copy.
- the system can generate a superset or subset of data from one or more big objects. Customers/tenants/organizations are free to create as many big objects of any size as they need.
- the system (by utilizing big objects) eliminates many boundaries to this thinking. By allowing customers/tenants/organizations to operate in terms of the how valuable this data is to them on a time basis, this allows for a good fit with immutable data—therefore the system allows the customer/tenant/organization to define the importance of their data based on how long they want to keep it.
- creating big objects can be available via typical user interface techniques, for example, using the custom object wizard experience, customers are free to define the full range field types, but with no limits to how many fields they define, or the data types they can use.
- big objects when created, are typically empty, and they can be populated with data from, for example, the current CRM database from the following sources: by creating clones of BPOs or custom objects, and/or by mapping fields from BPOs/custom object to a new big objects, and orchestrating data across with a timeline or other criteria. Big objects can also be populated from third-party sources, for example, via structured Data Ingest using our Bulk API and/or Data Loader where very large third-party data that is structured can be mapped to one or more big objects.
- data that is encapsulated by a big object may by definition not be sharable. In one embodiment, establishing and maintaining visibility to this data is controlled using a set of reference and custom permission sets. In one embodiment, data in an big object is by definition is immutable, so features that rely on a material data change to function may by definition be unavailable to big objects.
- One aspect of big objects is that the mechanism allows platform to manage large amounts of data, and provide the associated capabilities with these objects without data storage costs or scale being a consideration for the customer. Instead, the anticipated model may focus more on which objects are more important to retain for longer—on a per big object basis a customer may be able to set a retention policy that governs how long this data must be stored.
- FIG. 1 is a block diagram of one embodiment of an architecture that may provide big objects as described herein.
- client devices are used by one or more users to access services from a service provider.
- the service provided can be, for example, an on-demand services environment, a multitenant database environment, or any other type of service provider.
- Client devices 110 and 115 operate to allow a user to access remote services provided by service provider 140 via network 130 .
- Client devices 110 can be, for example, desktop computers, laptop computers, tablets, smart phones, thin clients, etc.
- Network 130 can be any network, for example, the Internet, a corporate local area network or wide area network, a cellular network, and/or any combination thereof.
- Service provider 140 can be any number of servers and/or other devices that operate to provide services to one or more client devices.
- service provider 140 operates with one or more relational databases (e.g., 150 ) and one or more non-relational databases (e.g., 160 ).
- Service provider 140 operates using relational database 150 and non-relational database 160 as described above.
- service provider 140 is an on-demand services environment with multiple client organizations that provides different and/or different levels of services to the client organizations.
- service provider 140 can be a multitenant database environment that provides custom interfaces and data isolation to the different client organizations.
- multitenant database environment the utilization of relational database 150 and non-relational database 160 can be on an organization-by-organization basis with different parameters and/or conditions for different organizations.
- service provider 140 operates using relational database 150 to provide custom objects, which are custom database tables that allow a customer/tenant/organization to store information unique to the customer/tenant/organization.
- custom objects are custom database tables that allow a customer/tenant/organization to store information unique to the customer/tenant/organization.
- an organization may create a custom object called “Quotes” to store data for the organization's sales quotes.
- the custom object can be used to, for example, create custom fields, associate the custom object with other records and display the custom object data in custom related lists, track tasks and events for custom object records, build page layouts, customize search results and the custom object fields that display them, create reports and dashboards to analyze custom object data, import custom object records.
- service provider 140 operates using non-relational database 160 to provide big objects as described above.
- the big objects can provide most or nearly all of the functionality of a custom object with increased scalability because non-relational database 160 can provide better scalability than relational database 150 .
- FIG. 2 is an interaction diagram of one embodiment of a technique for querying a non-relational (NoSQL) database using relational database (SQL) commands.
- the technique of FIG. 2 is performed within a multitenant database environment.
- SQL interface 210 is any type of interface/client device that can be used to receive SQL commands and provide results form the SQL commands.
- SQL interface 210 can be a SQL application running on a client computing device.
- SQL-to-NoSQL agent 220 provides the functionality described herein.
- SQL-to-NoSQL agent 220 may be a centralized single agent or can be distributed over multiple entities.
- Non-relational database 230 can be any type of non-relational database, for example, HBase.
- SQL interface 210 In response to receiving at least one SQL command representing a query, SQL interface 210 sends the query, 250 , to SQL-to-NoSQL agent 220 . In response to receiving the SQL command, SQL-to-NoSQL agent 220 parses the query, 252 . SQL-to-NoSQL agent 220 then compiles a query, which can include retrieving metadata, 254 , from non-relational database 230 . The query plan can be optimized, 256 . In one embodiment the SQL query is transformed into one or more scans that are relatively simple, for example, with no joins, basic filtering and/or simple aggregation.
- the scans can be run on a sub-section of tables so that not all tables need to be replicated in the non-relational database. In some embodiments, the results need only be approximately correct. Other optimizations can be utilized to provide the desired level of performance.
- the query plan can be executed as multiple parallel scans, 260 , of non-relational database 230 .
- a set of HBase (or other non-relational database) scans that can be executed in parallel for each row key range.
- these scans are executed in parallel for each row key range and can be combined to provide results of the query.
- non-relational database 230 can perform filtering and/or aggregation.
- Results of the multiple parallel scans are returned, 265 , to SQL-to-NoSQL agent 220 .
- SQL-to-NoSQL agent 220 can perform merge sorting on the results. By combining the results of the one or more scans, the system can provide an aggregated/unified result to the original SQL query. The results are provided, 270 , to SQL interface 210 .
- deletion from the relational database environment is decoupled from the copy process.
- a system job in the relational database environment periodically (e.g., daily, weekly, 12 hours) runs to query tenants/organizations that have the functionality described herein enabled to determine whether any data copy jobs have been completed. If so, the data that has been copied to the non-relational database environment may be deleted from the relational database environment.
- the handler determines the parameters (e.g., field history, older than a specified date) for the deletion request.
- the non-relational database can be queried to determine the data within the specified range.
- the handler passes identifiers loaded from the non-relational database environment to the relational database environment to cause a hard delete of the corresponding rows from the relational database environment. Loading the identifiers from the non-relational database environment to the relational database environment ensures that data will not be deleted before being successfully copied from the relational database environment to the non-relational database environment.
- FIG. 3 illustrates a block diagram of an environment 310 wherein an on-demand database service might be used.
- Environment 310 may include user systems 312 , network 314 , system 316 , processor system 317 , application platform 318 , network interface 320 , tenant data storage 322 , system data storage 324 , program code 326 , and process space 328 .
- environment 310 may not have all of the components listed and/or may have other elements instead of, or in addition to, those listed above.
- Environment 310 is an environment in which an on-demand database service exists.
- User system 312 may be any machine or system that is used by a user to access a database user system.
- any of user systems 312 can be a handheld computing device, a mobile phone, a laptop computer, a work station, and/or a network of computing devices.
- user systems 312 might interact via a network 314 with an on-demand database service, which is system 316 .
- An on-demand database service such as system 316
- system 316 is a database system that is made available to outside users that do not need to necessarily be concerned with building and/or maintaining the database system, but instead may be available for their use when the users need the database system (e.g., on the demand of the users).
- Some on-demand database services may store information from one or more tenants stored into tables of a common database image to form a multi-tenant database system (MTS). Accordingly, “on-demand database service 316 ” and “system 316 ” will be used interchangeably herein.
- a database image may include one or more database objects.
- Application platform 318 may be a framework that allows the applications of system 316 to run, such as the hardware and/or software, e.g., the operating system.
- on-demand database service 316 may include an application platform 318 that enables creation, managing and executing one or more applications developed by the provider of the on-demand database service, users accessing the on-demand database service via user systems 312 , or third party application developers accessing the on-demand database service via user systems 312 .
- the users of user systems 312 may differ in their respective capacities, and the capacity of a particular user system 312 might be entirely determined by permissions (permission levels) for the current user. For example, where a salesperson is using a particular user system 312 to interact with system 316 , that user system has the capacities allotted to that salesperson. However, while an administrator is using that user system to interact with system 316 , that user system has the capacities allotted to that administrator.
- users at one permission level may have access to applications, data, and database information accessible by a lower permission level user, but may not have access to certain applications, database information, and data accessible by a user at a higher permission level. Thus, different users will have different capabilities with regard to accessing and modifying application and database information, depending on a user's security or permission level.
- Network 314 is any network or combination of networks of devices that communicate with one another.
- network 314 can be any one or any combination of a LAN (local area network), WAN (wide area network), telephone network, wireless network, point-to-point network, star network, token ring network, hub network, or other appropriate configuration.
- LAN local area network
- WAN wide area network
- telephone network wireless network
- point-to-point network star network
- token ring network token ring network
- hub network or other appropriate configuration.
- TCP/IP Transfer Control Protocol and Internet Protocol
- User systems 312 might communicate with system 316 using TCP/IP and, at a higher network level, use other common Internet protocols to communicate, such as HTTP, FTP, AFS, WAP, etc.
- HTTP HyperText Transfer Protocol
- user system 312 might include an HTTP client commonly referred to as a “browser” for sending and receiving HTTP messages to and from an HTTP server at system 316 .
- HTTP server might be implemented as the sole network interface between system 316 and network 314 , but other techniques might be used as well or instead.
- the interface between system 316 and network 314 includes load sharing functionality, such as round-robin HTTP request distributors to balance loads and distribute incoming HTTP requests evenly over a plurality of servers. At least as for the users that are accessing that server, each of the plurality of servers has access to the MTS' data; however, other alternative configurations may be used instead.
- system 316 implements a web-based customer relationship management (CRM) system.
- system 316 includes application servers configured to implement and execute CRM software applications as well as provide related data, code, forms, webpages and other information to and from user systems 312 and to store to, and retrieve from, a database system related data, objects, and Webpage content.
- CRM customer relationship management
- system 316 includes application servers configured to implement and execute CRM software applications as well as provide related data, code, forms, webpages and other information to and from user systems 312 and to store to, and retrieve from, a database system related data, objects, and Webpage content.
- tenant data typically 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.
- system 316 implements applications other than, or in addition to, a CRM application.
- system 316 may provide tenant access to multiple hosted (standard and custom) applications, including a CRM application.
- User (or third party developer) applications which may or may not include CRM, may be supported by the application platform 318 , which manages creation, storage of the applications into one or more database objects and executing of the applications in a virtual machine in the process space of the system 316 .
- FIG. 3 One arrangement for elements of system 316 is shown in FIG. 3 , including a network interface 320 , application platform 318 , tenant data storage 322 for tenant data 323 , system data storage 324 for system data 325 accessible to system 316 and possibly multiple tenants, program code 326 for implementing various functions of system 316 , and a process space 328 for executing MTS system processes and tenant-specific processes, such as running applications as part of an application hosting service. Additional processes that may execute on system 316 include database indexing processes.
- each user system 312 could include a desktop personal computer, workstation, laptop, PDA, cell phone, or any wireless access protocol (WAP) enabled device or any other computing device capable of interfacing directly or indirectly to the Internet or other network connection.
- WAP wireless access protocol
- User system 312 typically runs an HTTP client, e.g., a browsing program, such as Microsoft's Internet Explorer browser, Netscape's Navigator browser, Opera's browser, or a WAP-enabled browser in the case of a cell phone, PDA or other wireless device, or the like, allowing a user (e.g., subscriber of the multi-tenant database system) of user system 312 to access, process and view information, pages and applications available to it from system 316 over network 314 .
- HTTP client e.g., a browsing program, such as Microsoft's Internet Explorer browser, Netscape's Navigator browser, Opera's browser, or a WAP-enabled browser in the case of a cell phone, PDA or other wireless device, or the like.
- Each user system 312 also typically includes one or more user interface devices, such as a keyboard, a mouse, trackball, touch pad, touch screen, pen or the like, for interacting with a graphical user interface (GUI) provided by the browser on a display (e.g., a monitor screen, LCD display, etc.) in conjunction with pages, forms, applications and other information provided by system 316 or other systems or servers.
- GUI graphical user interface
- the user interface device can be used to access data and applications hosted by system 316 , and to perform searches on stored data, and otherwise allow a user to interact with various GUI pages that may be presented to a user.
- embodiments are suitable for use with the Internet, which refers to a specific global internetwork of networks. However, it should be understood that other networks can be used instead of the Internet, such as an intranet, an extranet, a virtual private network (VPN), a non-TCP/IP based network, any LAN or WAN or the like.
- VPN virtual private network
- each user system 312 and all of its components are operator configurable using applications, such as a browser, including computer code run using a central processing unit such as an Intel Pentium® processor or the like.
- system 316 (and additional instances of an MTS, where more than one is present) and all of their components might be operator configurable using application(s) including computer code to run using a central processing unit such as processor system 317 , which may include an Intel Pentium® processor or the like, and/or multiple processor units.
- a computer program product embodiment includes a machine-readable storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the embodiments described herein.
- Computer code for operating and configuring system 316 to intercommunicate and to process webpages, applications and other data and media content as described herein are preferably downloaded and stored on a hard disk, but the entire program code, or portions thereof, may also be stored in any other volatile or non-volatile memory medium or device as is well known, such as a ROM or RAM, or provided on any media capable of storing program code, such as any type of rotating media including floppy disks, optical discs, digital versatile disk (DVD), compact disk (CD), microdrive, and magneto-optical disks, and magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.
- any type of rotating media including floppy disks, optical discs, digital versatile disk (DVD), compact disk (CD), microdrive, and magneto-optical disks, and magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.
- the entire program code, or portions thereof may be transmitted and downloaded from a software source over a transmission medium, e.g., over the Internet, or from another server, as is well known, or transmitted over any other conventional network connection as is well known (e.g., extranet, VPN, LAN, etc.) using any communication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as are well known.
- a transmission medium e.g., over the Internet
- any other conventional network connection e.g., extranet, VPN, LAN, etc.
- any communication medium and protocols e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.
- computer code for implementing embodiments can be implemented in any programming language that can be executed on a client system and/or server or server system such as, for example, C, C++, HTML, any other markup language, JavaTM, JavaScript, ActiveX, any other scripting language, such as VBScript, and many other programming languages as are well known may be used.
- JavaTM is a trademark of Sun Microsystems, Inc.
- each system 316 is configured to provide webpages, forms, applications, data and media content to user (client) systems 312 to support the access by user systems 312 as tenants of system 316 .
- system 316 provides security mechanisms to keep each tenant's data separate unless the data is shared.
- MTS Mobility Management Entity
- they may be located in close proximity to one another (e.g., in a server farm located in a single building or campus), or they may be distributed at locations remote from one another (e.g., one or more servers located in city A and one or more servers located in city B).
- each MTS could include one or more logically and/or physically connected servers distributed locally or across one or more geographic locations.
- server is meant to include a computer system, including processing hardware and process space(s), and an associated storage system and database application (e.g., OODBMS or RDBMS) as is well known in the art. It should also be understood that “server system” and “server” are often used interchangeably herein.
- database object described herein can be implemented as single databases, a distributed database, a collection of distributed databases, a database with redundant online or offline backups or other redundancies, etc., and might include a distributed database or storage network and associated processing intelligence.
- FIG. 4 also illustrates environment 310 . However, in FIG. 4 elements of system 316 and various interconnections in an embodiment are further illustrated.
- user system 312 may include processor system 312 A, memory system 312 B, input system 312 C, and output system 312 D.
- FIG. 4 shows network 314 and system 316 .
- system 316 may include tenant data storage 322 , tenant data 323 , system data storage 324 , system data 325 , User Interface (UI) 430 , Application Program Interface (API) 432 , PL/SOQL 434 , save routines 436 , application setup mechanism 438 , applications servers 400 1 - 400 N , system process space 402 , tenant process spaces 404 , tenant management process space 410 , tenant storage area 412 , user storage 414 , and application metadata 416 .
- environment 310 may not have the same elements as those listed above and/or may have other elements instead of, or in addition to, those listed above.
- processor system 312 A may be any combination of one or more processors.
- Memory system 312 B may be any combination of one or more memory devices, short term, and/or long term memory.
- Input system 312 C may be any combination of input devices, such as one or more keyboards, mice, trackballs, scanners, cameras, and/or interfaces to networks.
- Output system 312 D may be any combination of output devices, such as one or more monitors, printers, and/or interfaces to networks.
- system 316 may include a network interface 320 (of FIG.
- Each application server 400 may be configured to tenant data storage 322 and the tenant data 323 therein, and system data storage 324 and the system data 325 therein to serve requests of user systems 312 .
- the tenant data 323 might be divided into individual tenant storage areas 412 , which can be either a physical arrangement and/or a logical arrangement of data.
- user storage 414 and application metadata 416 might be similarly allocated for each user.
- a copy of a user's most recently used (MRU) items might be stored to user storage 414 .
- a copy of MRU items for an entire organization that is a tenant might be stored to tenant storage area 412 .
- a UI 430 provides a user interface and an API 432 provides an application programmer interface to system 316 resident processes to users and/or developers at user systems 312 .
- the tenant data and the system data may be stored in various databases, such as one or more OracleTM databases.
- Application platform 318 includes an application setup mechanism 438 that supports application developers' creation and management of applications, which may be saved as metadata into tenant data storage 322 by save routines 436 for execution by subscribers as one or more tenant process spaces 404 managed by tenant management process 410 for example. Invocations to such applications may be coded using PL/SOQL 434 that provides a programming language style interface extension to API 432 . A detailed description of some PL/SOQL language embodiments is discussed in commonly owned U.S. Pat. No. 7,730,478 entitled, “Method and System for Allowing Access to Developed Applicants via a Multi-Tenant Database On-Demand Database Service” issued Jun. 1, 2010 to Craig Weissman, which is incorporated in its entirety herein for all purposes. Invocations to applications may be detected by one or more system processes, which manage retrieving application metadata 416 for the subscriber making the invocation and executing the metadata as an application in a virtual machine.
- Each application server 400 may be communicably coupled to database systems, e.g., having access to system data 325 and tenant data 323 , via a different network connection.
- one application server 400 1 might be coupled via the network 314 (e.g., the Internet)
- another application server 400 N-1 might be coupled via a direct network link
- another application server 400 N might be coupled by yet a different network connection.
- Transfer Control Protocol and Internet Protocol TCP/IP
- TCP/IP Transfer Control Protocol and Internet Protocol
- each application server 400 is configured to handle requests for any user associated with any organization that is a tenant. Because it is desirable to be able to add and remove application servers from the server pool at any time for any reason, there is preferably no server affinity for a user and/or organization to a specific application server 400 .
- an interface system implementing a load balancing function e.g., an F5 Big-IP load balancer
- the load balancer uses a least connections algorithm to route user requests to the application servers 400 .
- Other examples of load balancing algorithms such as round robin and observed response time, also can be used.
- system 316 is multi-tenant, wherein system 316 handles storage of, and access to, different objects, data and applications across disparate users and organizations.
- one tenant might be a company that employs a sales force where each salesperson uses system 316 to manage their sales process.
- a user might maintain contact data, leads data, customer follow-up data, performance data, goals and progress data, etc., all applicable to that user's personal sales process (e.g., in tenant data storage 322 ).
- tenant data storage 322 e.g., in tenant data storage 322 .
- the user can manage his or her sales efforts and cycles from any of many different user systems. For example, if a salesperson is visiting a customer and the customer has Internet access in their lobby, the salesperson can obtain critical updates as to that customer while waiting for the customer to arrive in the lobby.
- user systems 312 (which may be client systems) communicate with application servers 400 to request and update system-level and tenant-level data from system 316 that may require sending one or more queries to tenant data storage 322 and/or system data storage 324 .
- System 316 e.g., an application server 400 in system 316
- System data storage 324 may generate query plans to access the requested data from the database.
- Each database can generally be viewed as a collection of objects, such as a set of logical tables, containing data fitted into predefined categories.
- a “table” is one representation of a data object, and may be used herein to simplify the conceptual description of objects and custom objects. It should be understood that “table” and “object” may be used interchangeably herein.
- Each table generally contains one or more data categories logically arranged as columns or fields in a viewable schema. Each row or record of a table contains an instance of data for each category defined by the fields.
- a CRM database may include a table that describes a customer with fields for basic contact information such as name, address, phone number, fax number, etc.
- Another table might describe a purchase order, including fields for information such as customer, product, sale price, date, etc.
- standard entity tables might be provided for use by all tenants.
- such standard entities might include tables for Account, Contact, Lead, and Opportunity data, each containing pre-defined fields. It should be understood that the word “entity” may also be used interchangeably herein with “object” and “table”.
- tenants may be allowed to create and store custom objects, or they may be allowed to customize standard entities or objects, for example by creating custom fields for standard objects, including custom index fields.
- all custom entity data rows are stored in a single multi-tenant physical table, which may contain multiple logical tables per organization. It is transparent to customers that their multiple “tables” are in fact stored in one large table or that their data may be stored in the same table as the data of other customers.
Abstract
Techniques and mechanisms to manage data. A relational database environment having at least a relational database storage device is coupled with a server entity. Data stored in the relational database is stored in a custom object, which is one or more custom database tables that allow a customer/tenant/organization to store information unique to the customer/tenant/organization. A non-relational database environment having at least a non-relational database storage device is also coupled with the server entity. Data stored in the non-relational database is immutable. A single user interface and search language is utilized by the server entity to provide access to both the relational database environment and the non-relational database environment.
Description
- This application is related to, and claims priority to, provisional utility application No. 61/904,822 entitled “SCALABLE OBJECTS,” filed on Nov. 15, 2013, and having attorney docket No. 1362PROV; provisional utility application No. 61/904,826 entitled “MULTI-TENANCY FOR A NOSQL DATABASE,” filed Nov. 15, 2013, and having attorney docket No. 1363PROV; provisional utility application No. 61/905,439 entitled “BIG OBJECTS,” filed Nov. 18, 2013, and having attorney docket No. 1364PROV; provisional utility application No. 61/905,457 entitled “ORCHESTRATION BETWEEN TWO MULTI-TENANT DATABASES,” filed Nov. 18, 2013, and having attorney docket No. 1365PROV; and provisional utility application No. 61/905,460 entitled “FIELD HISTORY RETENTION,” filed Nov. 18, 2013, and having attorney docket No. 1366PROV, the entire contents of which are all incorporated herein by reference.
- Embodiments relate to database management. More specifically, embodiments relate to providing services from both a relational database environment and a non-relational database environment.
- Any subject matter discussed in the background section should not be assumed to be prior art merely as a result of its mention in the background section. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches, which in and of themselves may also correspond to implementations of the claimed inventions.
- As service providers grow (in terms of numbers of customers and/or amount of customer data), data retention and management becomes more complex. With that growth comes the significant challenge of how to effectively and efficiently represent the increased volume of data. Object models and semantics that work at one level may not be effective with this growth. While the service provider is pushed to provide more suitable storage and/or semantics, customers want to continue to work within the same data model, platform and/or data accessibility.
- Embodiments of the invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements.
-
FIG. 1 is a block diagram of one embodiment of an architecture that may provide big objects as described herein. -
FIG. 2 is an interaction diagram of one embodiment of a technique for querying a non-relational (NoSQL) database using relational database (SQL) commands. -
FIG. 3 illustrates a block diagram of an environment where an on-demand database service might be used. -
FIG. 4 illustrates a block diagram of an environment where an on-demand database service might be provided. - In the following description, numerous specific details are set forth. However, embodiments of the invention may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description.
- For some on-demand services environments significant portions of data storage requirements can be used without using a relational database. However, a relational database may be needed for some data and/or may have been the basis for data when the services started. Data that does not require the relational database can be, for example, data that does not change over time, thus not requiring the ACID (Atomicity, Consistency, Isolation, Durability) properties of the relational database. In one embodiment, a new object type (sometimes referred to herein as a “big” object) is provide that can “unhook” customers/tenants/organizations from these constraints when it is desirable and/or appropriate to do so.
- In one embodiment, a system provides declarative and programmatic ways to construct and use these big objects. In one embodiment, the system can operate to create custom objects within the bounds of a relational database, such as an Oracle® database, and replumbing it to a higher scale. Custom objects are custom database tables that allow a user to store information unique to their organization. In one embodiment, the system creates objects through the Salesforce (SFDC) metadata application programming interface (API) and, yet, data goes to a non-relational (e.g., NoSQL) database, such as HBase instead. The NoSQL database can, in some instances, hold more information that is addressable from the SFDC platform. Similarly, in one implementation, all the standard features of Salesforce work with both the relational database and the non-relational database.
- For a typical application of the big objects as described herein, a customer/client/tenant will have a large volume of data to be stored, the data is historical in nature (can be considered immutable) and access to the data can be controlled by simple accessibility rules, and native platform sharing is not required. Use of the big objects as described herein can be accomplished with different types of data as well.
- The techniques herein allow customers/tenants/organizations to be unleashed from data limits that could interfere with application effectiveness. The Big Object feature set asserts a differentiating primitive—it allows customers/tenants/organizations to think at scale from the inception of their data, but also that these objects are conceived and used independent of the functional expectations and feature set of traditional base platform and custom objects.
- In one embodiment, the big objects utilize frameworks such as the the Metadata API from salesforce to push data to a NoSQL database such as HBase where vast amounts of data can quickly be analyzed, yet the system still provides the same functionality as a SQL server, in terms of allowing queries and other features to be implemented on the data. In one embodiment, the following behavior is assumed when utilizing big objects.
- Once created and populated, a big object, the data, in one implementation, is immutable—it cannot change its current form. Yet, the data has full API and SOQL access from the platform. Data immutability can force a consciousness on users to take a more prescriptive look on the data they have on the platform, which objects contain data that needs to change on a frequent basis, and which data does not need to change.
- In one embodiment, data mutations utilize a copy. In one embodiment, should any change in the data be required, the system can generate a superset or subset of data from one or more big objects. Customers/tenants/organizations are free to create as many big objects of any size as they need.
- Rather than having customers/tenants/organizations restrain their thinking as to how much data should or could have on a platform, the system (by utilizing big objects) eliminates many boundaries to this thinking. By allowing customers/tenants/organizations to operate in terms of the how valuable this data is to them on a time basis, this allows for a good fit with immutable data—therefore the system allows the customer/tenant/organization to define the importance of their data based on how long they want to keep it.
- In one embodiment, creating big objects can be available via typical user interface techniques, for example, using the custom object wizard experience, customers are free to define the full range field types, but with no limits to how many fields they define, or the data types they can use. In one embodiment, big objects, when created, are typically empty, and they can be populated with data from, for example, the current CRM database from the following sources: by creating clones of BPOs or custom objects, and/or by mapping fields from BPOs/custom object to a new big objects, and orchestrating data across with a timeline or other criteria. Big objects can also be populated from third-party sources, for example, via structured Data Ingest using our Bulk API and/or Data Loader where very large third-party data that is structured can be mapped to one or more big objects.
- In one embodiment, data that is encapsulated by a big object may by definition not be sharable. In one embodiment, establishing and maintaining visibility to this data is controlled using a set of reference and custom permission sets. In one embodiment, data in an big object is by definition is immutable, so features that rely on a material data change to function may by definition be unavailable to big objects.
- One aspect of big objects is that the mechanism allows platform to manage large amounts of data, and provide the associated capabilities with these objects without data storage costs or scale being a consideration for the customer. Instead, the anticipated model may focus more on which objects are more important to retain for longer—on a per big object basis a customer may be able to set a retention policy that governs how long this data must be stored.
-
FIG. 1 is a block diagram of one embodiment of an architecture that may provide big objects as described herein. In one embodiment, client devices are used by one or more users to access services from a service provider. The service provided can be, for example, an on-demand services environment, a multitenant database environment, or any other type of service provider. -
Client devices service provider 140 vianetwork 130.Client devices 110 can be, for example, desktop computers, laptop computers, tablets, smart phones, thin clients, etc. Network 130 can be any network, for example, the Internet, a corporate local area network or wide area network, a cellular network, and/or any combination thereof. -
Service provider 140 can be any number of servers and/or other devices that operate to provide services to one or more client devices. In one embodiment,service provider 140 operates with one or more relational databases (e.g., 150) and one or more non-relational databases (e.g., 160).Service provider 140 operates usingrelational database 150 andnon-relational database 160 as described above. - In one embodiment,
service provider 140 is an on-demand services environment with multiple client organizations that provides different and/or different levels of services to the client organizations. For example,service provider 140 can be a multitenant database environment that provides custom interfaces and data isolation to the different client organizations. In the example, multitenant database environment, the utilization ofrelational database 150 andnon-relational database 160 can be on an organization-by-organization basis with different parameters and/or conditions for different organizations. - In one embodiment,
service provider 140 operates usingrelational database 150 to provide custom objects, which are custom database tables that allow a customer/tenant/organization to store information unique to the customer/tenant/organization. For example, an organization may create a custom object called “Quotes” to store data for the organization's sales quotes. The custom object can be used to, for example, create custom fields, associate the custom object with other records and display the custom object data in custom related lists, track tasks and events for custom object records, build page layouts, customize search results and the custom object fields that display them, create reports and dashboards to analyze custom object data, import custom object records. - In one embodiment,
service provider 140 operates usingnon-relational database 160 to provide big objects as described above. The big objects can provide most or nearly all of the functionality of a custom object with increased scalability becausenon-relational database 160 can provide better scalability thanrelational database 150. -
FIG. 2 is an interaction diagram of one embodiment of a technique for querying a non-relational (NoSQL) database using relational database (SQL) commands. In one embodiment, the technique ofFIG. 2 is performed within a multitenant database environment. -
SQL interface 210 is any type of interface/client device that can be used to receive SQL commands and provide results form the SQL commands. For example,SQL interface 210 can be a SQL application running on a client computing device. SQL-to-NoSQL agent 220 provides the functionality described herein. SQL-to-NoSQL agent 220 may be a centralized single agent or can be distributed over multiple entities.Non-relational database 230 can be any type of non-relational database, for example, HBase. - In response to receiving at least one SQL command representing a query,
SQL interface 210 sends the query, 250, to SQL-to-NoSQL agent 220. In response to receiving the SQL command, SQL-to-NoSQL agent 220 parses the query, 252. SQL-to-NoSQL agent 220 then compiles a query, which can include retrieving metadata, 254, fromnon-relational database 230. The query plan can be optimized, 256. In one embodiment the SQL query is transformed into one or more scans that are relatively simple, for example, with no joins, basic filtering and/or simple aggregation. - In one embodiment, the scans can be run on a sub-section of tables so that not all tables need to be replicated in the non-relational database. In some embodiments, the results need only be approximately correct. Other optimizations can be utilized to provide the desired level of performance.
- The query plan can be executed as multiple parallel scans, 260, of
non-relational database 230. In one embodiment, a set of HBase (or other non-relational database) scans that can be executed in parallel for each row key range. In one embodiment, these scans are executed in parallel for each row key range and can be combined to provide results of the query. - In one embodiment,
non-relational database 230 can perform filtering and/or aggregation. Results of the multiple parallel scans are returned, 265, to SQL-to-NoSQL agent 220. In one embodiment, SQL-to-NoSQL agent 220 can perform merge sorting on the results. By combining the results of the one or more scans, the system can provide an aggregated/unified result to the original SQL query. The results are provided, 270, toSQL interface 210. - In one embodiment, deletion from the relational database environment is decoupled from the copy process. In embodiment, a system job in the relational database environment periodically (e.g., daily, weekly, 12 hours) runs to query tenants/organizations that have the functionality described herein enabled to determine whether any data copy jobs have been completed. If so, the data that has been copied to the non-relational database environment may be deleted from the relational database environment.
- In one embodiment, when a deletion message/job is processed, the handler determines the parameters (e.g., field history, older than a specified date) for the deletion request. The non-relational database can be queried to determine the data within the specified range. For each chunk, the handler passes identifiers loaded from the non-relational database environment to the relational database environment to cause a hard delete of the corresponding rows from the relational database environment. Loading the identifiers from the non-relational database environment to the relational database environment ensures that data will not be deleted before being successfully copied from the relational database environment to the non-relational database environment.
-
FIG. 3 illustrates a block diagram of anenvironment 310 wherein an on-demand database service might be used.Environment 310 may includeuser systems 312,network 314,system 316,processor system 317,application platform 318,network interface 320,tenant data storage 322,system data storage 324,program code 326, andprocess space 328. In other embodiments,environment 310 may not have all of the components listed and/or may have other elements instead of, or in addition to, those listed above. -
Environment 310 is an environment in which an on-demand database service exists.User system 312 may be any machine or system that is used by a user to access a database user system. For example, any ofuser systems 312 can be a handheld computing device, a mobile phone, a laptop computer, a work station, and/or a network of computing devices. As illustrated in hereinFIG. 3 (and in more detail inFIG. 4 )user systems 312 might interact via anetwork 314 with an on-demand database service, which issystem 316. - An on-demand database service, such as
system 316, is a database system that is made available to outside users that do not need to necessarily be concerned with building and/or maintaining the database system, but instead may be available for their use when the users need the database system (e.g., on the demand of the users). Some on-demand database services may store information from one or more tenants stored into tables of a common database image to form a multi-tenant database system (MTS). Accordingly, “on-demand database service 316” and “system 316” will be used interchangeably herein. A database image may include one or more database objects. A relational database management system (RDMS) or the equivalent may execute storage and retrieval of information against the database object(s).Application platform 318 may be a framework that allows the applications ofsystem 316 to run, such as the hardware and/or software, e.g., the operating system. In an embodiment, on-demand database service 316 may include anapplication platform 318 that enables creation, managing and executing one or more applications developed by the provider of the on-demand database service, users accessing the on-demand database service viauser systems 312, or third party application developers accessing the on-demand database service viauser systems 312. - The users of
user systems 312 may differ in their respective capacities, and the capacity of aparticular user system 312 might be entirely determined by permissions (permission levels) for the current user. For example, where a salesperson is using aparticular user system 312 to interact withsystem 316, that user system has the capacities allotted to that salesperson. However, while an administrator is using that user system to interact withsystem 316, that user system has the capacities allotted to that administrator. In systems with a hierarchical role model, users at one permission level may have access to applications, data, and database information accessible by a lower permission level user, but may not have access to certain applications, database information, and data accessible by a user at a higher permission level. Thus, different users will have different capabilities with regard to accessing and modifying application and database information, depending on a user's security or permission level. -
Network 314 is any network or combination of networks of devices that communicate with one another. For example,network 314 can be any one or any combination of a LAN (local area network), WAN (wide area network), telephone network, wireless network, point-to-point network, star network, token ring network, hub network, or other appropriate configuration. As the most common type of computer network in current use is a TCP/IP (Transfer Control Protocol and Internet Protocol) network, such as the global internetwork of networks often referred to as the “Internet” with a capital “I,” that network will be used in many of the examples herein. However, it should be understood that the networks that one or more implementations might use are not so limited, although TCP/IP is a frequently implemented protocol. -
User systems 312 might communicate withsystem 316 using TCP/IP and, at a higher network level, use other common Internet protocols to communicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTP is used,user system 312 might include an HTTP client commonly referred to as a “browser” for sending and receiving HTTP messages to and from an HTTP server atsystem 316. Such an HTTP server might be implemented as the sole network interface betweensystem 316 andnetwork 314, but other techniques might be used as well or instead. In some implementations, the interface betweensystem 316 andnetwork 314 includes load sharing functionality, such as round-robin HTTP request distributors to balance loads and distribute incoming HTTP requests evenly over a plurality of servers. At least as for the users that are accessing that server, each of the plurality of servers has access to the MTS' data; however, other alternative configurations may be used instead. - In one embodiment,
system 316, shown inFIG. 3 , implements a web-based customer relationship management (CRM) system. For example, in one embodiment,system 316 includes application servers configured to implement and execute CRM software applications as well as provide related data, code, forms, webpages and other information to and fromuser systems 312 and to store to, and retrieve from, a database system related data, objects, and Webpage content. With a multi-tenant system, data for multiple tenants may be stored in the same physical database object, however, tenant data typically 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. In certain embodiments,system 316 implements applications other than, or in addition to, a CRM application. For example,system 316 may provide tenant access to multiple hosted (standard and custom) applications, including a CRM application. User (or third party developer) applications, which may or may not include CRM, may be supported by theapplication platform 318, which manages creation, storage of the applications into one or more database objects and executing of the applications in a virtual machine in the process space of thesystem 316. - One arrangement for elements of
system 316 is shown inFIG. 3 , including anetwork interface 320,application platform 318,tenant data storage 322 fortenant data 323,system data storage 324 forsystem data 325 accessible tosystem 316 and possibly multiple tenants,program code 326 for implementing various functions ofsystem 316, and aprocess space 328 for executing MTS system processes and tenant-specific processes, such as running applications as part of an application hosting service. Additional processes that may execute onsystem 316 include database indexing processes. - Several elements in the system shown in
FIG. 3 include conventional, well-known elements that are explained only briefly here. For example, eachuser system 312 could include a desktop personal computer, workstation, laptop, PDA, cell phone, or any wireless access protocol (WAP) enabled device or any other computing device capable of interfacing directly or indirectly to the Internet or other network connection.User system 312 typically runs an HTTP client, e.g., a browsing program, such as Microsoft's Internet Explorer browser, Netscape's Navigator browser, Opera's browser, or a WAP-enabled browser in the case of a cell phone, PDA or other wireless device, or the like, allowing a user (e.g., subscriber of the multi-tenant database system) ofuser system 312 to access, process and view information, pages and applications available to it fromsystem 316 overnetwork 314. Eachuser system 312 also typically includes one or more user interface devices, such as a keyboard, a mouse, trackball, touch pad, touch screen, pen or the like, for interacting with a graphical user interface (GUI) provided by the browser on a display (e.g., a monitor screen, LCD display, etc.) in conjunction with pages, forms, applications and other information provided bysystem 316 or other systems or servers. For example, the user interface device can be used to access data and applications hosted bysystem 316, and to perform searches on stored data, and otherwise allow a user to interact with various GUI pages that may be presented to a user. As discussed above, embodiments are suitable for use with the Internet, which refers to a specific global internetwork of networks. However, it should be understood that other networks can be used instead of the Internet, such as an intranet, an extranet, a virtual private network (VPN), a non-TCP/IP based network, any LAN or WAN or the like. - According to one embodiment, each
user system 312 and all of its components are operator configurable using applications, such as a browser, including computer code run using a central processing unit such as an Intel Pentium® processor or the like. Similarly, system 316 (and additional instances of an MTS, where more than one is present) and all of their components might be operator configurable using application(s) including computer code to run using a central processing unit such asprocessor system 317, which may include an Intel Pentium® processor or the like, and/or multiple processor units. A computer program product embodiment includes a machine-readable storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the embodiments described herein. Computer code for operating and configuringsystem 316 to intercommunicate and to process webpages, applications and other data and media content as described herein are preferably downloaded and stored on a hard disk, but the entire program code, or portions thereof, may also be stored in any other volatile or non-volatile memory medium or device as is well known, such as a ROM or RAM, or provided on any media capable of storing program code, such as any type of rotating media including floppy disks, optical discs, digital versatile disk (DVD), compact disk (CD), microdrive, and magneto-optical disks, and magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data. Additionally, the entire program code, or portions thereof, may be transmitted and downloaded from a software source over a transmission medium, e.g., over the Internet, or from another server, as is well known, or transmitted over any other conventional network connection as is well known (e.g., extranet, VPN, LAN, etc.) using any communication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as are well known. It will also be appreciated that computer code for implementing embodiments can be implemented in any programming language that can be executed on a client system and/or server or server system such as, for example, C, C++, HTML, any other markup language, Java™, JavaScript, ActiveX, any other scripting language, such as VBScript, and many other programming languages as are well known may be used. (Java™ is a trademark of Sun Microsystems, Inc.). - According to one embodiment, each
system 316 is configured to provide webpages, forms, applications, data and media content to user (client)systems 312 to support the access byuser systems 312 as tenants ofsystem 316. As such,system 316 provides security mechanisms to keep each tenant's data separate unless the data is shared. If more than one MTS is used, they may be located in close proximity to one another (e.g., in a server farm located in a single building or campus), or they may be distributed at locations remote from one another (e.g., one or more servers located in city A and one or more servers located in city B). As used herein, each MTS could include one or more logically and/or physically connected servers distributed locally or across one or more geographic locations. Additionally, the term “server” is meant to include a computer system, including processing hardware and process space(s), and an associated storage system and database application (e.g., OODBMS or RDBMS) as is well known in the art. It should also be understood that “server system” and “server” are often used interchangeably herein. Similarly, the database object described herein can be implemented as single databases, a distributed database, a collection of distributed databases, a database with redundant online or offline backups or other redundancies, etc., and might include a distributed database or storage network and associated processing intelligence. -
FIG. 4 also illustratesenvironment 310. However, inFIG. 4 elements ofsystem 316 and various interconnections in an embodiment are further illustrated.FIG. 4 shows thatuser system 312 may includeprocessor system 312A,memory system 312B,input system 312C, andoutput system 312D.FIG. 4 showsnetwork 314 andsystem 316.FIG. 4 also shows thatsystem 316 may includetenant data storage 322,tenant data 323,system data storage 324,system data 325, User Interface (UI) 430, Application Program Interface (API) 432, PL/SOQL 434, saveroutines 436,application setup mechanism 438, applications servers 400 1-400 N,system process space 402,tenant process spaces 404, tenantmanagement process space 410,tenant storage area 412,user storage 414, andapplication metadata 416. In other embodiments,environment 310 may not have the same elements as those listed above and/or may have other elements instead of, or in addition to, those listed above. -
User system 312,network 314,system 316,tenant data storage 322, andsystem data storage 324 were discussed above inFIG. 3 . Regardinguser system 312,processor system 312A may be any combination of one or more processors.Memory system 312B may be any combination of one or more memory devices, short term, and/or long term memory.Input system 312C may be any combination of input devices, such as one or more keyboards, mice, trackballs, scanners, cameras, and/or interfaces to networks.Output system 312D may be any combination of output devices, such as one or more monitors, printers, and/or interfaces to networks. As shown byFIG. 4 ,system 316 may include a network interface 320 (ofFIG. 3 ) implemented as a set ofHTTP application servers 400, anapplication platform 318,tenant data storage 322, andsystem data storage 324. Also shown issystem process space 402, including individualtenant process spaces 404 and a tenantmanagement process space 410. Eachapplication server 400 may be configured to tenantdata storage 322 and thetenant data 323 therein, andsystem data storage 324 and thesystem data 325 therein to serve requests ofuser systems 312. Thetenant data 323 might be divided into individualtenant storage areas 412, which can be either a physical arrangement and/or a logical arrangement of data. Within eachtenant storage area 412,user storage 414 andapplication metadata 416 might be similarly allocated for each user. For example, a copy of a user's most recently used (MRU) items might be stored touser storage 414. Similarly, a copy of MRU items for an entire organization that is a tenant might be stored to tenantstorage area 412. AUI 430 provides a user interface and anAPI 432 provides an application programmer interface tosystem 316 resident processes to users and/or developers atuser systems 312. The tenant data and the system data may be stored in various databases, such as one or more Oracle™ databases. -
Application platform 318 includes anapplication setup mechanism 438 that supports application developers' creation and management of applications, which may be saved as metadata intotenant data storage 322 by saveroutines 436 for execution by subscribers as one or moretenant process spaces 404 managed bytenant management process 410 for example. Invocations to such applications may be coded using PL/SOQL 434 that provides a programming language style interface extension toAPI 432. A detailed description of some PL/SOQL language embodiments is discussed in commonly owned U.S. Pat. No. 7,730,478 entitled, “Method and System for Allowing Access to Developed Applicants via a Multi-Tenant Database On-Demand Database Service” issued Jun. 1, 2010 to Craig Weissman, which is incorporated in its entirety herein for all purposes. Invocations to applications may be detected by one or more system processes, which manage retrievingapplication metadata 416 for the subscriber making the invocation and executing the metadata as an application in a virtual machine. - Each
application server 400 may be communicably coupled to database systems, e.g., having access tosystem data 325 andtenant data 323, via a different network connection. For example, oneapplication server 400 1 might be coupled via the network 314 (e.g., the Internet), anotherapplication server 400 N-1 might be coupled via a direct network link, and anotherapplication server 400 N might be coupled by yet a different network connection. Transfer Control Protocol and Internet Protocol (TCP/IP) are typical protocols for communicating betweenapplication servers 400 and the database system. However, it will be apparent to one skilled in the art that other transport protocols may be used to optimize the system depending on the network interconnect used. - In certain embodiments, each
application server 400 is configured to handle requests for any user associated with any organization that is a tenant. Because it is desirable to be able to add and remove application servers from the server pool at any time for any reason, there is preferably no server affinity for a user and/or organization to aspecific application server 400. In one embodiment, therefore, an interface system implementing a load balancing function (e.g., an F5 Big-IP load balancer) is communicably coupled between theapplication servers 400 and theuser systems 312 to distribute requests to theapplication servers 400. In one embodiment, the load balancer uses a least connections algorithm to route user requests to theapplication servers 400. Other examples of load balancing algorithms, such as round robin and observed response time, also can be used. For example, in certain embodiments, three consecutive requests from the same user could hit threedifferent application servers 400, and three requests from different users could hit thesame application server 400. In this manner,system 316 is multi-tenant, whereinsystem 316 handles storage of, and access to, different objects, data and applications across disparate users and organizations. - As an example of storage, one tenant might be a company that employs a sales force where each salesperson uses
system 316 to manage their sales process. Thus, a user might maintain contact data, leads data, customer follow-up data, performance data, goals and progress data, etc., all applicable to that user's personal sales process (e.g., in tenant data storage 322). In an example of a MTS arrangement, since all of the data and the applications to access, view, modify, report, transmit, calculate, etc., can be maintained and accessed by a user system having nothing more than network access, the user can manage his or her sales efforts and cycles from any of many different user systems. For example, if a salesperson is visiting a customer and the customer has Internet access in their lobby, the salesperson can obtain critical updates as to that customer while waiting for the customer to arrive in the lobby. - While each user's data might be separate from other users' data regardless of the employers of each user, some data might be organization-wide data shared or accessible by a plurality of users or all of the users for a given organization that is a tenant. Thus, there might be some data structures managed by
system 316 that are allocated at the tenant level while other data structures might be managed at the user level. Because an MTS might support multiple tenants including possible competitors, the MTS should have security protocols that keep data, applications, and application use separate. Also, because many tenants may opt for access to an MTS rather than maintain their own system, redundancy, up-time, and backup are additional functions that may be implemented in the MTS. In addition to user-specific data and tenant specific data,system 316 might also maintain system level data usable by multiple tenants or other data. Such system level data might include industry reports, news, postings, and the like that are sharable among tenants. - In certain embodiments, user systems 312 (which may be client systems) communicate with
application servers 400 to request and update system-level and tenant-level data fromsystem 316 that may require sending one or more queries to tenantdata storage 322 and/orsystem data storage 324. System 316 (e.g., anapplication server 400 in system 316) automatically generates one or more SQL statements (e.g., one or more SQL queries) that are designed to access the desired information.System data storage 324 may generate query plans to access the requested data from the database. - Each database can generally be viewed as a collection of objects, such as a set of logical tables, containing data fitted into predefined categories. A “table” is one representation of a data object, and may be used herein to simplify the conceptual description of objects and custom objects. It should be understood that “table” and “object” may be used interchangeably herein. Each table generally contains one or more data categories logically arranged as columns or fields in a viewable schema. Each row or record of a table contains an instance of data for each category defined by the fields. For example, a CRM database may include a table that describes a customer with fields for basic contact information such as name, address, phone number, fax number, etc. Another table might describe a purchase order, including fields for information such as customer, product, sale price, date, etc. In some multi-tenant database systems, standard entity tables might be provided for use by all tenants. For CRM database applications, such standard entities might include tables for Account, Contact, Lead, and Opportunity data, each containing pre-defined fields. It should be understood that the word “entity” may also be used interchangeably herein with “object” and “table”.
- In some multi-tenant database systems, tenants may be allowed to create and store custom objects, or they may be allowed to customize standard entities or objects, for example by creating custom fields for standard objects, including custom index fields. U.S. patent application Ser. No. 10/817,161, filed Apr. 2, 2004, entitled “Custom Entities and Fields in a Multi-Tenant Database System”, and which is hereby incorporated herein by reference, teaches systems and methods for creating custom objects as well as customizing standard objects in a multi-tenant database system. In certain embodiments, for example, all custom entity data rows are stored in a single multi-tenant physical table, which may contain multiple logical tables per organization. It is transparent to customers that their multiple “tables” are in fact stored in one large table or that their data may be stored in the same table as the data of other customers.
- Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
- While the invention has been described in terms of several embodiments, those skilled in the art will recognize that the invention is not limited to the embodiments described, but can be practiced with modification and alteration within the spirit and scope of the appended claims. The description is thus to be regarded as illustrative instead of limiting.
Claims (20)
1. A system to manage data, the system comprising:
a server entity to provide service to one or more remote client devices;
a relational database system having at least a relational database storage device as part of a multitenant environment, the relational database system coupled with the server entity; and
a non-relational database system having at least a non-relational database storage device as part of the multitenant environment, the relational database system coupled with the server entity, wherein data stored in the non-relational database is immutable, wherein data stored in the non-relational database system is stored in a custom object, which is one or more custom database tables that allow a tenant to store information unique to the tenant;
wherein a single user interface and single search language is utilized by the server entity to provide access to both the relational database system and the non-relational database system.
2. The system of claim 1 wherein the server entity provides an on-demand services environment utilizing both the relational database environment and the non-relational database environment.
3. The system of claim 2 wherein the on-demand services environment comprises a multitenant database environment.
4. The system of claim 1 wherein the service provider is configurable to receive a Structure Query Language (SQL) query, to transform the SQL query into one or more non-relational database scans having associated row key ranges, to execute the one or more non-relational database scans in parallel for each row key range, to combine results from the parallel scans of the non-relational database, and to provide the combined results as results of the SQL query.
5. The system of claim 1 wherein data mutations utilize a copy operation so that changes in the data cause generation of a superset or of a subset of data.
6. A method for managing data within a database environment having a relational database and a non-relational database, the method comprising:
storing data in the relational database using a custom object comprising one or more database tables that allow a tenant of a multitenant environment to store information unique to the tenant using a first database interface;
storing immutable data in the non-relational database using a second database interface;
providing access to both the relational database and the non-relational database via the first database interface and the second database interface via a singe graphical user interface to receive database queries in a single search language for both the relational database and the non-relational database.
7. The method of claim 6 wherein providing access to both the relational database and the non-relational database via the first database interface and the second database interface via a singe graphical user interface comprises providing search functionality over data in both the relational database and the non-relational database via a single search mechanism.
8. The method of claim 6 wherein the database environment provides an on-demand services environment utilizing both the relational database environment and the non-relational database environment.
9. The method of claim 8 wherein the on-demand services environment comprises a multitenant database environment.
10. The method of claim 6 wherein the graphical user interface is configurable to receive a Structure Query Language (SQL) query, to transform the SQL query into one or more non-relational database scans having associated row key ranges, to execute the one or more non-relational database scans in parallel for each row key range, to combine results from the parallel scans of the non-relational database, and to provide the combined results as results of the SQL query.
11. The method of claim 6 wherein data mutations utilize a copy operation so that changes in the data cause generation of a superset or of a subset of data.
12. A non-transitory computer-readable medium having stored thereon instructions to provide data management within a database environment having a relational database and a non-relational database, the instructions, when executed by one or more processors, cause the one or more processors to:
store data in the relational database using a custom object comprising one or more database tables that allow a tenant of a multitenant environment to store information unique to the tenant using a first database interface;
store immutable data in the non-relational database using a second database interface;
provide access to both the relational database and the non-relational database via the first database interface and the second database interface via a singe graphical user interface to receive database queries in a single search language for both the relational database and the non-relational database.
13. The non-transitory computer-readable medium of claim 12 wherein the instructions that cause the one or more processors to provide access to both the relational database and the non-relational database via the first database interface and the second database interface via a singe graphical user interface comprise instructions that, when executed by the one or more processors, cause the one or more processors to provide search functionality over data in both the relational database and the non-relational database via a single search mechanism.
14. The non-transitory computer-readable medium of claim 12 wherein the database environment provides an on-demand services environment utilizing both the relational database environment and the non-relational database environment.
15. The non-transitory computer-readable medium of claim 14 wherein the on-demand services environment comprises a multitenant database environment.
16. The non-transitory computer-readable medium of claim 12 wherein the graphical user interface is configurable to receive a Structure Query Language (SQL) query, to transform the SQL query into one or more non-relational database scans having associated row key ranges, to execute the one or more non-relational database scans in parallel for each row key range, to combine results from the parallel scans of the non-relational database, and to provide the combined results as results of the SQL query.
17. The non-transitory computer-readable medium of claim 12 wherein data mutations utilize a copy operation so that changes in the data cause generation of a superset or of a subset of data.
18. An apparatus for managing data within a database environment having a relational database and a non-relational database, the apparatus comprising:
means for storing data in the relational database using a custom object comprising one or more database tables that allow a tenant of a multitenant environment to store information unique to the tenant using a first database interface;
means for storing immutable data in the non-relational database using a second database interface;
means for providing access to both the relational database and the non-relational database via the first database interface and the second database interface via a singe graphical user interface to receive database queries in a single search language for both the relational database and the non-relational database.
19. The apparatus of claim 18 wherein the means for providing access to both the relational database and the non-relational database via the first database interface and the second database interface via a singe graphical user interface comprise means for providing search functionality over data in both the relational database and the non-relational database via a single search mechanism.
20. The apparatus of claim 18 wherein the graphical user interface comprises means for receiving a Structured Query Language (SQL) query, to transform the SQL query into one or more non-relational database scans having associated row key ranges, to execute the one or more non-relational database scans in parallel for each row key range, to combine results from the parallel scans of the non-relational database, and to provide the combined results as results of the SQL query.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/542,338 US20150142844A1 (en) | 2013-11-15 | 2014-11-14 | Scalable objects for use in an on-demand services environment |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201361904826P | 2013-11-15 | 2013-11-15 | |
US201361904822P | 2013-11-15 | 2013-11-15 | |
US201361905439P | 2013-11-18 | 2013-11-18 | |
US201361905460P | 2013-11-18 | 2013-11-18 | |
US201361905457P | 2013-11-18 | 2013-11-18 | |
US14/542,338 US20150142844A1 (en) | 2013-11-15 | 2014-11-14 | Scalable objects for use in an on-demand services environment |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150142844A1 true US20150142844A1 (en) | 2015-05-21 |
Family
ID=53174354
Family Applications (10)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/542,342 Active 2035-07-20 US10366056B2 (en) | 2013-11-15 | 2014-11-14 | Asynchronous search for big objects |
US14/542,338 Abandoned US20150142844A1 (en) | 2013-11-15 | 2014-11-14 | Scalable objects for use in an on-demand services environment |
US14/542,353 Active 2036-05-20 US10628387B2 (en) | 2013-11-15 | 2014-11-14 | Techniques for data retention |
US14/542,348 Active 2035-12-25 US10061823B2 (en) | 2013-11-15 | 2014-11-14 | Multi-tenancy for structured query language (SQL) and non structured query language (NoSQL) databases |
US14/542,357 Active 2035-10-23 US10176235B2 (en) | 2013-11-15 | 2014-11-14 | Techniques for data retention |
US16/112,538 Active US10664487B2 (en) | 2013-11-15 | 2018-08-24 | Multi-tenancy for structured query language (SQL) and non structured query language (NoSQL) databases |
US16/442,409 Active 2035-12-31 US11615105B2 (en) | 2013-11-15 | 2019-06-14 | Asynchronous search for big objects |
US16/853,572 Active US11507589B2 (en) | 2013-11-15 | 2020-04-20 | Techniques for data retention |
US16/883,810 Active US11392599B2 (en) | 2013-11-15 | 2020-05-26 | Multi-tenancy for structured query language (SQL) and non structured query language (NOSQL) databases |
US18/049,117 Pending US20230084317A1 (en) | 2013-11-15 | 2022-10-24 | Techniques for data retention |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/542,342 Active 2035-07-20 US10366056B2 (en) | 2013-11-15 | 2014-11-14 | Asynchronous search for big objects |
Family Applications After (8)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/542,353 Active 2036-05-20 US10628387B2 (en) | 2013-11-15 | 2014-11-14 | Techniques for data retention |
US14/542,348 Active 2035-12-25 US10061823B2 (en) | 2013-11-15 | 2014-11-14 | Multi-tenancy for structured query language (SQL) and non structured query language (NoSQL) databases |
US14/542,357 Active 2035-10-23 US10176235B2 (en) | 2013-11-15 | 2014-11-14 | Techniques for data retention |
US16/112,538 Active US10664487B2 (en) | 2013-11-15 | 2018-08-24 | Multi-tenancy for structured query language (SQL) and non structured query language (NoSQL) databases |
US16/442,409 Active 2035-12-31 US11615105B2 (en) | 2013-11-15 | 2019-06-14 | Asynchronous search for big objects |
US16/853,572 Active US11507589B2 (en) | 2013-11-15 | 2020-04-20 | Techniques for data retention |
US16/883,810 Active US11392599B2 (en) | 2013-11-15 | 2020-05-26 | Multi-tenancy for structured query language (SQL) and non structured query language (NOSQL) databases |
US18/049,117 Pending US20230084317A1 (en) | 2013-11-15 | 2022-10-24 | Techniques for data retention |
Country Status (1)
Country | Link |
---|---|
US (10) | US10366056B2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180095790A1 (en) * | 2016-09-30 | 2018-04-05 | Salesforce.Com, Inc. | Scheduling jobs for processing log files using a database system |
US10693952B2 (en) | 2017-10-23 | 2020-06-23 | Salesforce.Com, Inc. | Technologies for low latency messaging |
JP2020525938A (en) * | 2017-06-27 | 2020-08-27 | セールスフォース ドット コム インコーポレイティッド | System and method for creating and deleting tenants in a database |
US11252119B2 (en) * | 2018-06-04 | 2022-02-15 | Salesforce.Com, Inc. | Message logging using two-stage message logging mechanisms |
Families Citing this family (58)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8977735B2 (en) * | 2011-12-12 | 2015-03-10 | Rackspace Us, Inc. | Providing a database as a service in a multi-tenant environment |
US9594771B2 (en) * | 2014-01-16 | 2017-03-14 | Courage Services, Inc. | System for analysis and geospatial visualization |
US9348870B2 (en) * | 2014-02-06 | 2016-05-24 | International Business Machines Corporation | Searching content managed by a search engine using relational database type queries |
US10346188B1 (en) * | 2014-06-13 | 2019-07-09 | Veritas Technologies Llc | Booting virtual machine instances in a distributed data processing architecture |
US9754001B2 (en) | 2014-08-18 | 2017-09-05 | Richard Banister | Method of integrating remote databases by automated client scoping of update requests prior to download via a communications network |
US10795856B1 (en) * | 2014-12-29 | 2020-10-06 | EMC IP Holding Company LLC | Methods, systems, and computer readable mediums for implementing a data protection policy for a transferred enterprise application |
US10838983B2 (en) | 2015-01-25 | 2020-11-17 | Richard Banister | Method of integrating remote databases by parallel update requests over a communications network |
US20160224594A1 (en) * | 2015-02-03 | 2016-08-04 | Simba Technologies Inc. | Schema Definition Tool |
US10642863B2 (en) * | 2015-05-27 | 2020-05-05 | Kaseya International Limited | Management of structured, non-structured, and semi-structured data in a multi-tenant environment |
US10824636B2 (en) * | 2015-05-27 | 2020-11-03 | Kaseya International Limited | Mechanisms for querying disparate data storage systems |
CN106445727A (en) * | 2015-08-07 | 2017-02-22 | 中国移动通信集团重庆有限公司 | Data backup method and system, and data recovery method and system |
US11138223B2 (en) * | 2015-09-09 | 2021-10-05 | LiveData, Inc. | Techniques for uniting multiple databases and related systems and methods |
US10838827B2 (en) * | 2015-09-16 | 2020-11-17 | Richard Banister | System and method for time parameter based database restoration |
US10657123B2 (en) | 2015-09-16 | 2020-05-19 | Sesame Software | Method and system for reducing time-out incidence by scoping date time stamp value ranges of succeeding record update requests in view of previous responses |
US10540237B2 (en) | 2015-09-16 | 2020-01-21 | Sesame Software, Inc. | System and method for procedure for point-in-time recovery of cloud or database data and records in whole or in part |
CN105550296B (en) * | 2015-12-10 | 2018-10-30 | 深圳市华讯方舟软件技术有限公司 | A kind of data lead-in method based on spark-SQL big data processing platforms |
US10423586B2 (en) * | 2016-03-17 | 2019-09-24 | Wipro Limited | Method and system for synchronization of relational database management system to non-structured query language database |
CN105843879B (en) * | 2016-03-21 | 2019-07-09 | 刘春阳 | Heterogeneous types database storage system based on CD and the method using the system |
US9900302B2 (en) | 2016-06-22 | 2018-02-20 | FinancialForce.com, Inc. | Seamless authentication for an application development platform |
US10984359B2 (en) * | 2016-06-23 | 2021-04-20 | FinancialForce.com, Inc. | Combining batch and queueable technologies in a salesforce platform for large volume parallel processing |
US10248702B2 (en) * | 2016-07-29 | 2019-04-02 | International Business Machines Corporation | Integration management for structured and unstructured data |
CN107798019A (en) * | 2016-09-07 | 2018-03-13 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus for being used to provide the node serve data for accelerating service node |
CN107741937B (en) * | 2016-09-13 | 2020-04-28 | 腾讯科技(深圳)有限公司 | Data query method and device |
US10496741B2 (en) | 2016-09-21 | 2019-12-03 | FinancialForce.com, Inc. | Dynamic intermediate templates for richly formatted output |
US10380094B2 (en) | 2016-09-30 | 2019-08-13 | Salesforce.Com, Inc. | Custom multi-tenant non-relational platform objects |
CA3038529A1 (en) * | 2016-09-30 | 2018-04-05 | Salesforce.Com, Inc. | Multi-tenant non-relational platform objects |
US10908947B2 (en) * | 2016-12-09 | 2021-02-02 | Salesforce.Com, Inc. | Big object bulk data ingest |
US10430602B2 (en) | 2016-12-16 | 2019-10-01 | International Business Machines Corporation | Tape processing offload to object storage |
US11290532B2 (en) | 2016-12-16 | 2022-03-29 | International Business Machines Corporation | Tape reconstruction from object storage |
US10417036B2 (en) * | 2017-02-24 | 2019-09-17 | Oracle International Corporation | Evaluation techniques for fast access to structured, semi-structured and unstructured data using a virtual machine that provides support for dynamic code generation |
US20180307735A1 (en) * | 2017-04-19 | 2018-10-25 | Ca, Inc. | Integrating relational and non-relational databases |
US11663205B2 (en) * | 2017-05-04 | 2023-05-30 | Salesforce, Inc. | Technologies for asynchronous querying |
US20190057101A1 (en) * | 2017-08-21 | 2019-02-21 | Salesforce.Com, Inc. | Efficient deletion of archive records after expiration of a tenant-defined retention period |
US11360976B2 (en) | 2017-08-31 | 2022-06-14 | Oracle International Corporation | Deployment of javascript and typescript stored procedures and user-defined functions into database management systems |
US10652309B2 (en) * | 2017-09-19 | 2020-05-12 | FinancialForce.com, Inc. | Mechanism to allow a messaging system to automatically switch to asynchronous operation due to high demand |
US11068617B2 (en) * | 2017-10-09 | 2021-07-20 | Sage Intacct, Inc. | Secure access to multi-tenant relational data |
US11038689B2 (en) | 2018-03-01 | 2021-06-15 | FinancialForce.com, Inc. | Efficient block chain generation |
US10846481B2 (en) | 2018-06-29 | 2020-11-24 | FinancialForce.com, Inc. | Method and system for bridging disparate platforms to automate a natural language interface |
CN109344608B (en) * | 2018-08-10 | 2021-09-21 | 天地融科技股份有限公司 | Information transmission method and system |
US11157466B2 (en) | 2018-09-04 | 2021-10-26 | Salesforce.Com, Inc. | Data templates associated with non-relational database systems |
US11093493B1 (en) | 2018-09-28 | 2021-08-17 | Amazon Technologies, Inc. | Dynamically switching between query and scan for optimizing table reads |
US11200143B2 (en) | 2019-01-08 | 2021-12-14 | FinancialForce.com, Inc. | Software development framework for a cloud computing platform |
CN109918393A (en) * | 2019-01-28 | 2019-06-21 | 武汉慧联无限科技有限公司 | The data platform and its data query and multilist conjunctive query method of Internet of Things |
CN110032604B (en) | 2019-02-02 | 2021-12-07 | 北京奥星贝斯科技有限公司 | Data storage device, translation device and database access method |
US10922485B2 (en) | 2019-07-10 | 2021-02-16 | FinancialForce.com, Inc. | Platform interpretation of user input converted into standardized input |
US11507786B2 (en) | 2019-11-04 | 2022-11-22 | FinancialForce.com, Inc. | Dynamic generation of client-specific feature maps |
US11397736B2 (en) | 2020-01-27 | 2022-07-26 | Salesforce, Inc. | Large scale data ingestion |
US11817201B2 (en) * | 2020-09-08 | 2023-11-14 | Medtronic, Inc. | Imaging discovery utility for augmenting clinical image management |
US11222021B2 (en) * | 2020-10-05 | 2022-01-11 | Business Mobile Ag | Technique for accessing archive data stored in relational databases through the SAP archive information system |
WO2022108461A1 (en) * | 2020-11-23 | 2022-05-27 | Goldenline Spolka Z Ograniczona Odpowiedzialnoscia | A system and method for managing and processing data in a dispersed environment with incompatible data storage sources |
US11409755B2 (en) | 2020-12-30 | 2022-08-09 | Elasticsearch B.V. | Asynchronous search of electronic assets via a distributed search engine |
US11899677B2 (en) | 2021-04-27 | 2024-02-13 | Elasticsearch B.V. | Systems and methods for automatically curating query responses |
US11734279B2 (en) | 2021-04-29 | 2023-08-22 | Elasticsearch B.V. | Event sequences search |
US11816075B2 (en) | 2021-07-27 | 2023-11-14 | Bank Of America Corporation | Configuration engine for dynamically generating user interfaces |
US11860867B2 (en) * | 2021-08-25 | 2024-01-02 | Walmart Apollo, Llc | Optimizing scans using query planning on batch data |
US11907776B2 (en) | 2022-03-04 | 2024-02-20 | Target Brands, Inc. | Integrated asynchronous access interface for data retrieval from distributed data sources |
US20230359605A1 (en) * | 2022-05-09 | 2023-11-09 | Salesforce, Inc. | Autonomous Refactoring System for Database |
CN116303730B (en) * | 2023-05-18 | 2023-08-01 | 安徽泛联信息科技有限公司 | Asynchronous data source connection system for data visualization platform |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110258179A1 (en) * | 2010-04-19 | 2011-10-20 | Salesforce.Com | Methods and systems for optimizing queries in a multi-tenant store |
US20110258225A1 (en) * | 2010-04-19 | 2011-10-20 | Salesforce.Com, Inc. | Methods and Systems for Performing Transparent Object Migration Across Storage Tiers |
US20140149400A1 (en) * | 2012-11-26 | 2014-05-29 | Accenture Global Services Limited | Data consistency management |
Family Cites Families (130)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5649104A (en) | 1993-03-19 | 1997-07-15 | Ncr Corporation | System for allowing user of any computer to draw image over that generated by the host computer and replicating the drawn image to other computers |
US5608872A (en) | 1993-03-19 | 1997-03-04 | Ncr Corporation | System for allowing all remote computers to perform annotation on an image and replicating the annotated image on the respective displays of other comuters |
US5577188A (en) | 1994-05-31 | 1996-11-19 | Future Labs, Inc. | Method to provide for virtual screen overlay |
GB2300991B (en) | 1995-05-15 | 1997-11-05 | Andrew Macgregor Ritchie | Serving signals to browsing clients |
US5715450A (en) | 1995-09-27 | 1998-02-03 | Siebel Systems, Inc. | Method of selecting and presenting data from a database using a query language to a user of a computer system |
US5831610A (en) | 1996-02-23 | 1998-11-03 | Netsuite Development L.P. | Designing networks |
US5821937A (en) | 1996-02-23 | 1998-10-13 | Netsuite Development, L.P. | Computer method for updating a network design |
US6604117B2 (en) | 1996-03-19 | 2003-08-05 | Siebel Systems, Inc. | Method of maintaining a network of partially replicated database system |
US5873096A (en) | 1997-10-08 | 1999-02-16 | Siebel Systems, Inc. | Method of maintaining a network of partially replicated database system |
US5884299A (en) | 1997-02-06 | 1999-03-16 | Ncr Corporation | Optimization of SQL queries involving aggregate expressions using a plurality of local and global aggregation operations |
WO1998038583A1 (en) | 1997-02-26 | 1998-09-03 | Siebel Systems, Inc. | Method of determining visibility to a remote database client of a plurality of database transactions having variable visibility strengths |
WO1998038586A1 (en) | 1997-02-26 | 1998-09-03 | Siebel Systems, Inc. | Method of determining the visibility to a remote databaseclient of a plurality of database transactions using simplified visibility rules |
AU6440398A (en) | 1997-02-26 | 1998-09-18 | Siebel Systems, Inc. | Method of using a cache to determine the visibility to a remote database client of a plurality of database transactions |
WO1998038762A2 (en) | 1997-02-26 | 1998-09-03 | Siebel Systems, Inc. | Determining visibility to a remote database client |
WO1998040804A2 (en) | 1997-02-26 | 1998-09-17 | Siebel Systems, Inc. | Distributed relational database |
AU6183798A (en) | 1997-02-27 | 1998-09-29 | Siebel Systems, Inc. | Method of migrating to a successive level of a software distribution incorporating local modifications |
WO1998040805A2 (en) | 1997-02-27 | 1998-09-17 | Siebel Systems, Inc. | Method of synchronizing independently distributed software and database schema |
AU6669198A (en) | 1997-02-28 | 1998-09-18 | Siebel Systems, Inc. | Partially replicated distributed database with multiple levels of remote clients |
US20020069077A1 (en) | 1997-05-19 | 2002-06-06 | Westport Benefits, L.L.C. | Computerized system for customizing and managing benefits |
US6169534B1 (en) | 1997-06-26 | 2001-01-02 | Upshot.Com | Graphical user interface for customer information management |
US6560461B1 (en) | 1997-08-04 | 2003-05-06 | Mundi Fomukong | Authorized location reporting paging system |
US5918159A (en) | 1997-08-04 | 1999-06-29 | Fomukong; Mundi | Location reporting satellite paging system with optional blocking of location reporting |
US20020059095A1 (en) | 1998-02-26 | 2002-05-16 | Cook Rachael Linette | System and method for generating, capturing, and managing customer lead information over a computer network |
US6732111B2 (en) | 1998-03-03 | 2004-05-04 | Siebel Systems, Inc. | Method, apparatus, system, and program product for attaching files and other objects to a partially replicated database |
US5963953A (en) | 1998-03-30 | 1999-10-05 | Siebel Systems, Inc. | Method, and system for product configuration |
CA2341871A1 (en) | 1998-08-27 | 2000-03-09 | Upshot Corporation | A method and apparatus for network-based sales force management |
US6601087B1 (en) | 1998-11-18 | 2003-07-29 | Webex Communications, Inc. | Instant document sharing |
US6728960B1 (en) | 1998-11-18 | 2004-04-27 | Siebel Systems, Inc. | Techniques for managing multiple threads in a browser environment |
US6549908B1 (en) | 1998-11-18 | 2003-04-15 | Siebel Systems, Inc. | Methods and apparatus for interpreting user selections in the context of a relation distributed as a set of orthogonalized sub-relations |
EP1135723A4 (en) | 1998-11-30 | 2005-02-16 | Siebel Systems Inc | Development tool, method, and system for client server applications |
EP1163604A4 (en) | 1998-11-30 | 2002-01-09 | Siebel Systems Inc | Assignment manager |
EP1196882A1 (en) | 1998-11-30 | 2002-04-17 | Siebel Systems, Inc. | Smart scripting call centers |
JP2002531899A (en) | 1998-11-30 | 2002-09-24 | シーベル システムズ,インコーポレイティド | State model for process monitoring |
US20020072951A1 (en) | 1999-03-03 | 2002-06-13 | Michael Lee | Marketing support database management method, system and program product |
US6574635B2 (en) | 1999-03-03 | 2003-06-03 | Siebel Systems, Inc. | Application instantiation based upon attributes and values stored in a meta data repository, including tiering of application layers objects and components |
US6339772B1 (en) | 1999-07-06 | 2002-01-15 | Compaq Computer Corporation | System and method for performing database operations on a continuous stream of tuples |
US6621834B1 (en) | 1999-11-05 | 2003-09-16 | Raindance Communications, Inc. | System and method for voice transmission over network protocols |
US6535909B1 (en) | 1999-11-18 | 2003-03-18 | Contigo Software, Inc. | System and method for record and playback of collaborative Web browsing session |
US6324568B1 (en) | 1999-11-30 | 2001-11-27 | Siebel Systems, Inc. | Method and system for distributing objects over a network |
US6654032B1 (en) | 1999-12-23 | 2003-11-25 | Webex Communications, Inc. | Instant sharing of documents on a remote server |
US7266502B2 (en) | 2000-03-31 | 2007-09-04 | Siebel Systems, Inc. | Feature centric release manager method and system |
US6732100B1 (en) | 2000-03-31 | 2004-05-04 | Siebel Systems, Inc. | Database access method and system for user role defined access |
US6336137B1 (en) | 2000-03-31 | 2002-01-01 | Siebel Systems, Inc. | Web client-server system and method for incompatible page markup and presentation languages |
US6577726B1 (en) | 2000-03-31 | 2003-06-10 | Siebel Systems, Inc. | Computer telephony integration hotelling method and system |
US20020087552A1 (en) | 2000-04-12 | 2002-07-04 | Samba Holdings, Inc. | Methods and systems for providing access to information via query application and output interface application |
US6434550B1 (en) | 2000-04-14 | 2002-08-13 | Rightnow Technologies, Inc. | Temporal updates of relevancy rating of retrieved information in an information search system |
US7730072B2 (en) | 2000-04-14 | 2010-06-01 | Rightnow Technologies, Inc. | Automated adaptive classification system for knowledge networks |
US6665655B1 (en) | 2000-04-14 | 2003-12-16 | Rightnow Technologies, Inc. | Implicit rating of retrieved information in an information search system |
US6842748B1 (en) | 2000-04-14 | 2005-01-11 | Rightnow Technologies, Inc. | Usage based strength between related information in an information retrieval system |
US6763501B1 (en) | 2000-06-09 | 2004-07-13 | Webex Communications, Inc. | Remote document serving |
KR100365357B1 (en) | 2000-10-11 | 2002-12-18 | 엘지전자 주식회사 | Method for data communication of mobile terminal |
US7581230B2 (en) | 2001-02-06 | 2009-08-25 | Siebel Systems, Inc. | Adaptive communication application programming interface |
USD454139S1 (en) | 2001-02-20 | 2002-03-05 | Rightnow Technologies | Display screen for a computer |
US7174514B2 (en) | 2001-03-28 | 2007-02-06 | Siebel Systems, Inc. | Engine to present a user interface based on a logical structure, such as one for a customer relationship management system, across a web site |
US6829655B1 (en) | 2001-03-28 | 2004-12-07 | Siebel Systems, Inc. | Method and system for server synchronization with a computing device via a companion device |
US7363388B2 (en) | 2001-03-28 | 2008-04-22 | Siebel Systems, Inc. | Method and system for direct server synchronization with a computing device |
US20030018705A1 (en) | 2001-03-31 | 2003-01-23 | Mingte Chen | Media-independent communication server |
US20030206192A1 (en) | 2001-03-31 | 2003-11-06 | Mingte Chen | Asynchronous message push to web browser |
US6732095B1 (en) | 2001-04-13 | 2004-05-04 | Siebel Systems, Inc. | Method and apparatus for mapping between XML and relational representations |
US7761288B2 (en) | 2001-04-30 | 2010-07-20 | Siebel Systems, Inc. | Polylingual simultaneous shipping of software |
US6711565B1 (en) | 2001-06-18 | 2004-03-23 | Siebel Systems, Inc. | Method, apparatus, and system for previewing search results |
US6728702B1 (en) | 2001-06-18 | 2004-04-27 | Siebel Systems, Inc. | System and method to implement an integrated search center supporting a full-text search and query on a database |
US6763351B1 (en) | 2001-06-18 | 2004-07-13 | Siebel Systems, Inc. | Method, apparatus, and system for attaching search results |
US6782383B2 (en) | 2001-06-18 | 2004-08-24 | Siebel Systems, Inc. | System and method to implement a persistent and dismissible search center frame |
US20030004971A1 (en) | 2001-06-29 | 2003-01-02 | Gong Wen G. | Automatic generation of data models and accompanying user interfaces |
US6826582B1 (en) | 2001-09-28 | 2004-11-30 | Emc Corporation | Method and system for using file systems for content management |
US7761535B2 (en) | 2001-09-28 | 2010-07-20 | Siebel Systems, Inc. | Method and system for server synchronization with a computing device |
US6724399B1 (en) | 2001-09-28 | 2004-04-20 | Siebel Systems, Inc. | Methods and apparatus for enabling keyboard accelerators in applications implemented via a browser |
US6993712B2 (en) | 2001-09-28 | 2006-01-31 | Siebel Systems, Inc. | System and method for facilitating user interaction in a browser environment |
US6978445B2 (en) | 2001-09-28 | 2005-12-20 | Siebel Systems, Inc. | Method and system for supporting user navigation in a browser environment |
US6901595B2 (en) | 2001-09-29 | 2005-05-31 | Siebel Systems, Inc. | Method, apparatus, and system for implementing a framework to support a web-based application |
US7962565B2 (en) | 2001-09-29 | 2011-06-14 | Siebel Systems, Inc. | Method, apparatus and system for a mobile web client |
US8359335B2 (en) | 2001-09-29 | 2013-01-22 | Siebel Systems, Inc. | Computing system and method to implicitly commit unsaved data for a world wide web application |
US7146617B2 (en) | 2001-09-29 | 2006-12-05 | Siebel Systems, Inc. | Method, apparatus, and system for implementing view caching in a framework to support web-based applications |
US7289949B2 (en) | 2001-10-09 | 2007-10-30 | Right Now Technologies, Inc. | Method for routing electronic correspondence based on the level and type of emotion contained therein |
US6915314B2 (en) | 2001-12-11 | 2005-07-05 | Adtech-Gesi, Llc | System for archiving and retrieving data from a database |
US6804330B1 (en) | 2002-01-04 | 2004-10-12 | Siebel Systems, Inc. | Method and system for accessing CRM data via voice |
US7058890B2 (en) | 2002-02-13 | 2006-06-06 | Siebel Systems, Inc. | Method and system for enabling connectivity to a data system |
US7131071B2 (en) | 2002-03-29 | 2006-10-31 | Siebel Systems, Inc. | Defining an approval process for requests for approval |
US7672853B2 (en) | 2002-03-29 | 2010-03-02 | Siebel Systems, Inc. | User interface for processing requests for approval |
US6850949B2 (en) | 2002-06-03 | 2005-02-01 | Right Now Technologies, Inc. | System and method for generating a dynamic interface via a communications network |
US20030229610A1 (en) * | 2002-06-07 | 2003-12-11 | Van Treeck George Michael | Simpler and more concise interface to relational databases |
US7594181B2 (en) | 2002-06-27 | 2009-09-22 | Siebel Systems, Inc. | Prototyping graphical user interfaces |
US7437720B2 (en) | 2002-06-27 | 2008-10-14 | Siebel Systems, Inc. | Efficient high-interactivity user interface for client-server applications |
US8639542B2 (en) | 2002-06-27 | 2014-01-28 | Siebel Systems, Inc. | Method and apparatus to facilitate development of a customer-specific business process model |
US20040010489A1 (en) | 2002-07-12 | 2004-01-15 | Rightnow Technologies, Inc. | Method for providing search-specific web pages in a network computing environment |
US7251787B2 (en) | 2002-08-28 | 2007-07-31 | Siebel Systems, Inc. | Method and apparatus for an integrated process modeller |
US9448860B2 (en) | 2003-03-21 | 2016-09-20 | Oracle America, Inc. | Method and architecture for providing data-change alerts to external applications via a push service |
US7904340B2 (en) | 2003-03-24 | 2011-03-08 | Siebel Systems, Inc. | Methods and computer-readable medium for defining a product model |
EP1606740A4 (en) | 2003-03-24 | 2007-10-03 | Siebel Systems Inc | Common common object |
WO2004086197A2 (en) | 2003-03-24 | 2004-10-07 | Siebel Systems, Inc. | Custom common object |
US8762415B2 (en) | 2003-03-25 | 2014-06-24 | Siebel Systems, Inc. | Modeling of order data |
US7685515B2 (en) | 2003-04-04 | 2010-03-23 | Netsuite, Inc. | Facilitating data manipulation in a browser-based user interface of an enterprise business application |
US7620655B2 (en) | 2003-05-07 | 2009-11-17 | Enecto Ab | Method, device and computer program product for identifying visitors of websites |
US7409336B2 (en) | 2003-06-19 | 2008-08-05 | Siebel Systems, Inc. | Method and system for searching data based on identified subset of categories and relevance-scored text representation-category combinations |
US20040260659A1 (en) | 2003-06-23 | 2004-12-23 | Len Chan | Function space reservation system |
US7237227B2 (en) | 2003-06-30 | 2007-06-26 | Siebel Systems, Inc. | Application user interface template with free-form layout |
US7694314B2 (en) | 2003-08-28 | 2010-04-06 | Siebel Systems, Inc. | Universal application network architecture |
US7302564B2 (en) | 2003-12-24 | 2007-11-27 | I-Net Software Gmbh | Translation of secure communications for handshake protocols |
US7197520B1 (en) * | 2004-04-14 | 2007-03-27 | Veritas Operating Corporation | Two-tier backup mechanism |
US7289976B2 (en) | 2004-12-23 | 2007-10-30 | Microsoft Corporation | Easy-to-use data report specification |
US8126870B2 (en) * | 2005-03-28 | 2012-02-28 | Sybase, Inc. | System and methodology for parallel query optimization using semantic-based partitioning |
US7958159B1 (en) * | 2005-12-19 | 2011-06-07 | Teradata Us, Inc. | Performing actions based on monitoring execution of a query |
US8954500B2 (en) | 2008-01-04 | 2015-02-10 | Yahoo! Inc. | Identifying and employing social network relationships |
US7933916B2 (en) | 2008-02-28 | 2011-04-26 | Microsoft Corporation | Querying nonSQL data stores with a SQL-style language |
US8538942B2 (en) * | 2008-09-12 | 2013-09-17 | Salesforce.Com, Inc. | Method and system for sharing documents between on-demand services |
US9143341B2 (en) | 2008-11-07 | 2015-09-22 | Opanga Networks, Inc. | Systems and methods for portable data storage devices that automatically initiate data transfers utilizing host devices |
US8112607B2 (en) | 2009-05-07 | 2012-02-07 | Sap Ag | Method and system for managing large write-once tables in shadow page databases |
US8666974B2 (en) * | 2010-04-16 | 2014-03-04 | Salesforce.Com, Inc. | Methods and systems for performing high volume searches in a multi-tenant store |
US10162851B2 (en) | 2010-04-19 | 2018-12-25 | Salesforce.Com, Inc. | Methods and systems for performing cross store joins in a multi-tenant store |
US9411907B2 (en) * | 2010-04-26 | 2016-08-09 | Salesforce.Com, Inc. | Method and system for performing searches in a multi-tenant database environment |
US9886483B1 (en) * | 2010-04-29 | 2018-02-06 | Quest Software Inc. | System for providing structured query language access to non-relational data stores |
US9262452B2 (en) * | 2010-05-07 | 2016-02-16 | Salesforce.Com, Inc. | Methods and systems for storing emails in a multi-tenant database system |
US8655867B2 (en) * | 2010-05-13 | 2014-02-18 | Salesforce.Com, Inc. | Method and system for optimizing queries in a multi-tenant database environment |
US8762340B2 (en) | 2010-05-14 | 2014-06-24 | Salesforce.Com, Inc. | Methods and systems for backing up a search index in a multi-tenant database environment |
US8386471B2 (en) | 2010-05-27 | 2013-02-26 | Salesforce.Com, Inc. | Optimizing queries in a multi-tenant database system environment |
US8918439B2 (en) * | 2010-06-17 | 2014-12-23 | International Business Machines Corporation | Data lifecycle management within a cloud computing environment |
US20120036146A1 (en) | 2010-10-26 | 2012-02-09 | ParElastic Corporation | Apparatus for elastic database processing with heterogeneous data |
US8819060B2 (en) * | 2010-11-19 | 2014-08-26 | Salesforce.Com, Inc. | Virtual objects in an on-demand database environment |
EP2705419A4 (en) | 2011-05-05 | 2015-04-15 | Reversinglabs Internat Gmbh | Database system and method |
US20130024484A1 (en) * | 2011-07-22 | 2013-01-24 | International Business Machines Corporation | System management in datacenter using a non-relational database |
US8959114B2 (en) * | 2011-10-21 | 2015-02-17 | Salesforce.Com, Inc. | Entitlement management in an on-demand system |
US9465844B2 (en) * | 2012-04-30 | 2016-10-11 | Sap Se | Unified table query processing |
TWI490716B (en) | 2012-12-07 | 2015-07-01 | Ind Tech Res Inst | Method for developing multi-tenant application and data accessing method of multi-tenant application and system using the same |
US9053210B2 (en) | 2012-12-14 | 2015-06-09 | Microsoft Technology Licensing, Llc | Graph query processing using plurality of engines |
US9104762B1 (en) | 2013-01-14 | 2015-08-11 | Amazon Technologies, Inc. | Universal database management |
US20140214897A1 (en) * | 2013-01-31 | 2014-07-31 | Yuankai Zhu | SYSTEMS AND METHODS FOR ACCESSING A NoSQL DATABASE USING BUSINESS INTELLIGENCE TOOLS |
US9507607B2 (en) | 2013-05-10 | 2016-11-29 | Vmware, Inc. | Virtual persistence |
US9785643B1 (en) | 2013-09-06 | 2017-10-10 | Veritas Technologies Llc | Systems and methods for reclaiming storage space in deduplicating data systems |
US10635644B2 (en) | 2013-11-11 | 2020-04-28 | Amazon Technologies, Inc. | Partition-based data stream processing framework |
-
2014
- 2014-11-14 US US14/542,342 patent/US10366056B2/en active Active
- 2014-11-14 US US14/542,338 patent/US20150142844A1/en not_active Abandoned
- 2014-11-14 US US14/542,353 patent/US10628387B2/en active Active
- 2014-11-14 US US14/542,348 patent/US10061823B2/en active Active
- 2014-11-14 US US14/542,357 patent/US10176235B2/en active Active
-
2018
- 2018-08-24 US US16/112,538 patent/US10664487B2/en active Active
-
2019
- 2019-06-14 US US16/442,409 patent/US11615105B2/en active Active
-
2020
- 2020-04-20 US US16/853,572 patent/US11507589B2/en active Active
- 2020-05-26 US US16/883,810 patent/US11392599B2/en active Active
-
2022
- 2022-10-24 US US18/049,117 patent/US20230084317A1/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110258179A1 (en) * | 2010-04-19 | 2011-10-20 | Salesforce.Com | Methods and systems for optimizing queries in a multi-tenant store |
US20110258225A1 (en) * | 2010-04-19 | 2011-10-20 | Salesforce.Com, Inc. | Methods and Systems for Performing Transparent Object Migration Across Storage Tiers |
US20140149400A1 (en) * | 2012-11-26 | 2014-05-29 | Accenture Global Services Limited | Data consistency management |
Non-Patent Citations (2)
Title |
---|
Dean, Jeffrey, and Sanjay Ghemawat. "MapReduce: simplified data processing on large clusters." Communications of the ACM 51.1 (2008): 107-113. * |
Shook, Adam, and Donald Miner. MapReduce Design Patterns. " O'Reilly Media, Inc.", (2012): Chapter 4. * |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180095790A1 (en) * | 2016-09-30 | 2018-04-05 | Salesforce.Com, Inc. | Scheduling jobs for processing log files using a database system |
US10275281B2 (en) * | 2016-09-30 | 2019-04-30 | Salesforce.Com, Inc. | Scheduling jobs for processing log files using a database system |
JP2020525938A (en) * | 2017-06-27 | 2020-08-27 | セールスフォース ドット コム インコーポレイティッド | System and method for creating and deleting tenants in a database |
US11500836B2 (en) * | 2017-06-27 | 2022-11-15 | Salesforce, Inc. | Systems and methods of creation and deletion of tenants within a database |
US10693952B2 (en) | 2017-10-23 | 2020-06-23 | Salesforce.Com, Inc. | Technologies for low latency messaging |
US11252119B2 (en) * | 2018-06-04 | 2022-02-15 | Salesforce.Com, Inc. | Message logging using two-stage message logging mechanisms |
Also Published As
Publication number | Publication date |
---|---|
US20150142846A1 (en) | 2015-05-21 |
US11392599B2 (en) | 2022-07-19 |
US20210011911A1 (en) | 2021-01-14 |
US10664487B2 (en) | 2020-05-26 |
US11507589B2 (en) | 2022-11-22 |
US20190303352A1 (en) | 2019-10-03 |
US11615105B2 (en) | 2023-03-28 |
US20200320071A1 (en) | 2020-10-08 |
US20150142736A1 (en) | 2015-05-21 |
US10176235B2 (en) | 2019-01-08 |
US20150142751A1 (en) | 2015-05-21 |
US10366056B2 (en) | 2019-07-30 |
US10061823B2 (en) | 2018-08-28 |
US20180365299A1 (en) | 2018-12-20 |
US20230084317A1 (en) | 2023-03-16 |
US10628387B2 (en) | 2020-04-21 |
US20150142783A1 (en) | 2015-05-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11615105B2 (en) | Asynchronous search for big objects | |
US9378263B2 (en) | Method and system for creating indices and loading key-value pairs for NoSQL databases | |
US8925041B2 (en) | System, method and computer program product for performing one or more actions based on a determined access permissions for a plurality of users | |
US11271995B2 (en) | Partition balancing in an on-demand services environment | |
US8818938B2 (en) | System, method and computer program product for synchronizing entities within a system | |
US10621372B2 (en) | Method and system for generating database access objects | |
US20170053014A1 (en) | Records management | |
US20140372484A1 (en) | Database multiplexing architectures | |
US20210232563A1 (en) | Techniques and architectures for data field lifecycle management | |
US11295068B2 (en) | Techniques and architectures for native data field lifecycle management | |
US20200272456A1 (en) | Techniques and Architectures for Maintaining Metadata Version Controls | |
US20210240738A1 (en) | Methods and systems for organization extensibility and cluster scalability | |
US20110282833A1 (en) | Providing administrative capabilities in a multi-tenant database environment | |
US20140075455A1 (en) | System, method and computer program product for publishing an application-independent format event | |
US20220092048A1 (en) | Techniques and Architectures for Providing an Extract-Once Framework Across Multiple Data Sources | |
US11314767B2 (en) | Techniques and architectures for managing cascading mutations in an environment having a data lake | |
US9495430B2 (en) | Systems and methods for batch processing of data records in an on-demand system | |
US9767133B2 (en) | Systems and methods for alternative change processes for changes to data objects |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SALESFORCE.COM, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BRUCE, JONATHAN MARK;LEVINE, ELI;TOENS, SIMON;REEL/FRAME:034187/0550 Effective date: 20141113 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |