# US 8,280,874 B2 · Multi-tenant database system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 8,280,874 B2
- Document ID: US8280874B2
- Status: Granted
- Kind: B2
- Application number: 12/776,252
- Filed: 2010-05-07
- Published: 2010-11-04
- Granted: 2012-10-02
- Earliest claimed: 2003-09-23
- Assignees: salesforce.com, inc.
- Inventors: Craig Weissman; Dave Moellenhoff; Simon Wong; Paul Nakada
- Web page: https://patentgrep.com/patent/US8280874B2

## CPC

- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 16/2453: Query optimisation
- G06F 16/2462: {Approximate or statistical queries}
- Y10S 707/99932: Access augmentation or optimizing
- Y10S 707/99933: Query processing, i.e. searching
- Y10S 707/99934: Query formulation, input preparation, or translation
- Y10S 707/99935: Query augmenting and refining, e.g. inexact access
- Y10S 707/99938: Concurrency, e.g. lock management in shared database
- Y10S 707/99939: Privileged access
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## Abstract

More efficient querying of a multi-tenant database using dynamic tuning of database indices. A layer of meta-data associates data items with tenants, e.g., via tags, and the meta-data is used to optimize searches by channeling processing resources during a query to only those pieces of data bearing the relevant tenant's unique tag.

## Claims

### Claim 1

A system for optimizing database queries in a multi-tenant database system, comprising:
a processor coupled to a memory;
a customer relationship management database having one or more data tables, wherein one or more of the data tables describe a customer and a sale associated with the customer;
a statistics generating module configured to generate tenant-level statistics for one or more tenants for the one or more data tables;
a query optimization module, configured to optimize a database query based on the tenant level statistics;
an application server configured to execute customer relationship management software applications, wherein the application server stores to, and retrieves from customer data from the customer relationship management database; and
a load balancer associated with the application server to route requests to the application server.

### Claim 2 (depends on 1)

The system of claim 1, wherein the customer relationship management database structure is fixed.

### Claim 3 (depends on 1)

The system of claim 1, wherein the multi-tenant system is configured to keep tenant's data separate unless the data is shared.

### Claim 4 (depends on 1)

The system of claim 1 further comprising a module for tracking metadata information to make choices about query access paths.

### Claim 5 (depends on 1)

The system of claim 1, wherein the customer relationship management database contains a plurality of customizable fields.

### Claim 6 (depends on 1)

The system of claim 1, wherein the multi-tenant database implements at least one protocol that keeps applications and application use separate.

### Claim 7

A computer program code embodied on a non-transitory computer readable medium for optimizing database queries in a multi-tenant database system, comprising:
computer code for generating tenant-level statistics for one or more tenants for one or more data tables of a customer relationship management database of a multi-tenant database system, wherein at least one of the data tables describe a customer and a sale associated with the customer;
computer code for optimizing a database query based on the tenant-level statistics; computer code for executing customer relationship management software applications, wherein an application server stores to, and retrieves from customer data from the customer relationship management database; and
computer code for routing requests to the application server using a load balancer associated with the application server.

### Claim 8 (depends on 7)

The computer program code of claim 7, wherein the customer relationship management database structure is fixed.

### Claim 9 (depends on 7)

The computer program code of claim 7, wherein the multi-tenant system is configured to keep tenant's data separate unless the data is shared.

### Claim 10 (depends on 7)

The computer program code of claim 7, further comprising computer code for tracking metadata information to make choices about query access paths.

### Claim 11 (depends on 7)

The computer program code of claim 7, wherein the customer relationship management database contains a plurality of customizable fields.

### Claim 12 (depends on 7)

The computer program code of claim 7, wherein the multi-tenant database implements at least one protocol that keeps applications and application use separate.

### Claim 13

A method for optimizing database queries in a multi-tenant database system, comprising:
generating tenant-level statistics for one or more tenants for one or more data tables of a customer relationship management database of a multi-tenant database system, wherein at least one of the data tables describe a customer and a sale associated with the customer;
optimizing a database query based on the tenant-level statistics;
executing customer relationship management software applications, wherein an application server stores to, and retrieves from customer data from the customer relationship management database; and
routing requests to the application server using a load balancer associated with the application server.

### Claim 14 (depends on 13)

The method of claim 13, wherein the customer relationship management database structure is fixed.

### Claim 15 (depends on 13)

The method of claim 13, wherein the multi-tenant system is configured to keep tenant's data separate unless the data is shared.

### Claim 16 (depends on 13)

The method of claim 13 further comprising tracking metadata information to make choices about query access paths.

### Claim 17 (depends on 13)

The method of claim 13, wherein the customer relationship management database contains a plurality of customizable fields.

### Claim 18 (depends on 13)

The method of claim 13, wherein the multi-tenant database implements at least one protocol that keeps applications and application use separate.
