Directing requests to databases based on client account association

Patent metadata

Field	Value
Publication number	US-12461939-B2
Application number	US-202418931781-A
Country	US
Kind code	B2
Filing date	Oct 30, 2024
Priority date	Jul 6, 2018
Publication date	Nov 4, 2025
Grant date	Nov 4, 2025

Abstract

Systems of methods of directing requests to databases based on client account association is disclosed. A method includes determining a first client account associated with a first request to perform a first transaction. The method includes determining a second client account associated with a second request to perform a second transaction. The method includes selecting, for the first request, a primary deployment that stores a first dataset responsive to determining the first client account associated with the first request. The method includes selecting, for the second request, a secondary deployment that stores a second dataset that includes the first dataset responsive to determining the second client account associated with the second request. The method includes executing, while the primary deployment and the secondary deployment are both available, the first transaction on the first dataset at the primary deployment and the second transaction on the second dataset at the secondary deployment.

First claim

What is claimed is:

1 . A system comprising:
a cache memory to store datasets; and a processor, operatively coupled with the cache memory, to:
determine a first client account associated with a first request to perform a first transaction;
determine a second client account associated with a second request to perform a second transaction;
select, for the first request, a primary deployment that stores a first dataset responsive to determining the first client account associated with the first request;
select, for the second request, a secondary deployment that stores a second dataset that comprises the first dataset responsive to determining the second client account associated with the second request; and
execute, while the primary deployment and the secondary deployment are both available, the first transaction on the first dataset at the primary deployment and the second transaction on the second dataset at the secondary deployment.

2 . The system of claim 1 , wherein the processor to:
propagate the second transaction on the second dataset to the primary deployment; and execute queries on the second dataset at the primary deployment.

3 . The system of claim 1 , wherein the processor to:
determine that the first dataset stored in the primary deployment is unavailable.

4 . The system of claim 3 , wherein to determine that the first dataset stored in the primary deployment is unavailable, the processor to:
determine that a power outage has occurred at the primary deployment, or determine that an error resulting in improper modification or deletion of the first dataset at the primary deployment has occurred.

5 . The system of claim 3 , wherein to determine that the first dataset stored in the primary deployment is unavailable, the processor to:
determine that a data center outage has occurred at the primary deployment.

6 . The system of claim 3 , wherein to determine that the first dataset stored in the primary deployment is unavailable, the processor to:
determine that a cloud provider of the primary deployment has experienced an outage.

7 . The system of claim 3 , wherein to determine that the first dataset stored in the primary deployment is unavailable, the processor to:
determine that an error has occurred at the primary deployment.

8 . The system of claim 3 , wherein to determine that the first dataset stored in the primary deployment is unavailable, the processor to:
determine that the primary deployment is undergoing scheduled downtime.

9 . The system of claim 1 , wherein the first dataset stored on the primary deployment is an encrypted version of the first dataset that is generated based on a first encryption key and the second dataset stored on the secondary deployment is an encrypted version of the second dataset that is generated based on a second encryption key.

10 . The system of claim 1 , wherein the processor to:
copy the first dataset stored in the primary deployment to a first region of the secondary deployment to cause the secondary deployment to copy the first dataset to a second region of the secondary deployment.

11 . A method, comprising:
determining a first client account associated with a first request to perform a first transaction; determining a second client account associated with a second request to perform a second transaction; selecting, for the first request, a primary deployment that stores a first dataset responsive to determining the first client account associated with the first request; selecting, for the second request, a secondary deployment that stores a second dataset that comprises the first dataset responsive to determining the second client account associated with the second request; and executing, while the primary deployment and the secondary deployment are both available, the first transaction on the first dataset at the primary deployment and the second transaction on the second dataset at the secondary deployment.

12 . The method of claim 11 , further comprising:
propagating the second transaction on the second dataset to the primary deployment; and executing queries on the second dataset at the primary deployment.

13 . The method of claim 11 , further comprising:
determining that the first dataset stored in the primary deployment is unavailable.

14 . The method of claim 13 , wherein determining that the first dataset stored in the primary deployment is unavailable further comprises:
determining that a power outage has occurred at the primary deployment; or determining that an error resulting in improper modification or deletion of the first dataset at the primary deployment has occurred.

15 . The method of claim 13 , wherein determining that the first dataset stored in the primary deployment is unavailable further comprises:
determining that a data center outage has occurred at the primary deployment.

16 . The method of claim 13 , wherein determining that the first dataset stored in the primary deployment is unavailable further comprises:
determining that a cloud provider of the primary deployment has experienced an outage.

17 . The method of claim 13 , wherein determining that the first dataset stored in the primary deployment is unavailable further comprises:
determining that an error has occurred at the primary deployment.

18 . The method of claim 13 , wherein determining that the first dataset stored in the primary deployment is unavailable further comprises:
determining that the primary deployment is undergoing scheduled downtime.

19 . The method of claim 11 , wherein the first dataset stored on the primary deployment is an encrypted version of the first dataset that is generated based on a first encryption key and the second dataset stored on the secondary deployment is an encrypted version of the second dataset that is generated based on a second encryption key.

20 . The method of claim 11 , further comprising:
copying the first dataset stored in the primary deployment to a first region of the secondary deployment to cause the secondary deployment to copy the first dataset to a second region of the secondary deployment.

21 . A non-transitory computer readable storage media comprising instructions that, when executed by a processor, cause the processor to:
determine a first client account associated with a first request to perform a first transaction; determine a second client account associated with a second request to perform a second transaction; select, for the first request, a primary deployment that stores a first dataset responsive to determining the first client account associated with the first request; select, for the second request, a secondary deployment that stores a second dataset that comprises the first dataset responsive to determining the second client account associated with the second request; and execute, while the primary deployment and the secondary deployment are both available, the first transaction on the first dataset at the primary deployment and the second transaction on the second dataset at the secondary deployment.

22 . The non-transitory computer readable storage media of claim 21 , wherein the processor to:
propagate the second transaction on the second dataset to the primary deployment; and execute queries on the second dataset at the primary deployment.

23 . The non-transitory computer readable storage media of claim 21 , wherein the processor to:
de

Assignees

• Snowflake Inc

Inventors

• Dageville Benoit
• Robinson Eric
• Hentschel Martin

Classifications

• G06F16/245

  Query processing · CPC title

• H04L67/1097

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title

• G06F16/2308

  Concurrency control (transaction processing G06F9/466) · CPC title

• G06F16/273 Primary

  Asynchronous replication or reconciliation · CPC title