Automated database replication using replication preparation objects

US11989206B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11989206-B2
Application numberUS-202217815375-A
CountryUS
Kind codeB2
Filing dateJul 27, 2022
Priority dateMar 21, 2021
Publication dateMay 21, 2024
Grant dateMay 21, 2024

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Techniques for database replication using replication preparation objects include storing, by at least one hardware processor, at least one task object at a remote deployment of a data provider. A replication request originating from an account of a data consumer is detected at the remote deployment using the at least one task object. The replication request is associated with a database available at a primary deployment of the data provider. Responsive to the detecting of the replication request, a local instance of the database is generated at the remote deployment. The account of the data consumer at the remote deployment is configured to access the local instance of the database.

First claim

Opening claim text (preview).

What is claimed is: 1. A system comprising: at least one hardware processor; and at least one memory storing instructions that cause the at least one hardware processor to perform operations comprising: storing at least one task object at a remote deployment of a data provider; detecting, using the at least one task object, a replication request originating from an account of a data consumer at the remote deployment, the replication request associated with a database available at a primary deployment of the data provider; responsive to the detecting of the replication request, generating a local instance of the database at the remote deployment, the generating of the local instance based on invoking a database refresh operation and pushing database data of the database available at the primary deployment to a database shell at the remote deployment in response to the database refresh operation, the pushing causing modifying of the database shell from an empty shell without the database data into a remote deployment database shell configured as the local instance of the database, and the remote deployment database shell including the database data of the primary deployment based on completion of the pushing; and configuring the account of the data consumer at the remote deployment to access the local instance of the database. 2. The system of claim 1 , the operations further comprising: storing, at the remote deployment of the data provider, a set of replication preparation objects, the set of replication preparation objects including the database shell, a share shell, and the at least one task object. 3. The system of claim 2 , the operations further comprising: monitoring using the at least one task object, the remote deployment for requests to replicate the database; and detecting the replication request based on the monitoring. 4. The system of claim 3 , the operations further comprising: in response to the detecting of the replication request, executing, by the at least one hardware processor, a set of data processing operations to cause the generating of the local instance. 5. The system of claim 2 , wherein the set of replication preparation objects is provisioned at the remote deployment of the data provider prior to the detecting of the replication request. 6. The system of claim 5 , the operations further comprising: in response to the detecting of the replication request, executing, by the at least one hardware processor, a set of data processing operations to invoke a database refresh operation using the database shell. 7. The system of claim 6 , the operations further comprising: configuring the database shell with the database data at the remote deployment as the local instance of the database; and granting the account of the data consumer at the remote deployment, access to share data in the remote deployment database shell using the share shell. 8. The system of claim 2 , the operations further comprising: executing a set data processing operations to invoke a share refresh operation that provides the account of the data consumer at the remote deployment with access to share data of the database. 9. The system of claim 8 , wherein the operations for invoking the share-refresh operation further comprise: initiating the pushing of the share data of the database from a share object at the primary deployment to the share shell of the set of replication preparation objects. 10. A method comprising: storing, by at least one hardware processor, at least one task object at a remote deployment of a data provider; detecting, using the at least one task object, a replication request originating from an account of a data consumer at the remote deployment, the replication request associated with a database available at a primary deployment of the data provider; responsive to the detecting of the replication request, generating a local instance of the database at the remote deployment, the generating of the local instance based on invoking a database refresh operation and pushing database data of the database available at the primary deployment to a database shell at the remote deployment in response to the database refresh operation, the pushing causing modifying of the database shell from an empty shell without the database data into a remote deployment database shell configured as the local instance of the database, and the remote deployment database shell including the database data of the primary deployment based on completion of the pushing; and configuring the account of the data consumer at the remote deployment to access the local instance of the database. 11. The method of claim 10 , further comprising: storing, at the remote deployment of the data provider, a set of replication preparation objects, the set of replication preparation objects including the database shell, a share shell, and the at least one task object. 12. The method of claim 11 , further comprising: monitoring using the at least one task object, the remote deployment for requests to replicate the database; and detecting the replication request based on the monitoring. 13. The method of claim 12 , further comprising: in response to the detecting of the replication request, executing, by the at least one hardware processor, a set of data processing operations to cause the generating of the local instance. 14. The method of claim 11 , wherein the set of replication preparation objects is provisioned at the remote deployment of the data provider prior to the detecting of the replication request. 15. The method of claim 14 , further comprising: in response to the detecting of the replication request, executing, by the at least one hardware processor, a set of data processing operations to invoke a database refresh operation using the database shell. 16. The method of claim 15 , further comprising: configuring the database shell with the database data at the remote deployment as the local instance of the database; and granting the account of the data consumer at the remote deployment, access to share data in the remote deployment database shell using the share shell. 17. The method of claim 11 , further comprising: executing a set of data processing operations to invoke a share-refresh operation that provides the account of the data consumer at the remote deployment with access to share data of the database. 18. The method of claim 17 , wherein invoking the share-refresh operation further comprises: initiating the pushing of the share data of the database from a share object at the primary deployment to the share shell of the set of replication preparation objects. 19. A non-transitory computer-storage medium comprising instructions that, when executed by one or more processors of a machine, configure the machine to perform operations comprising: storing at least one task object at a remote deployment of a data provider; detecting, using the at least one task object, a replication request originating from an account of a data consumer at the remote deployment, the replication request associated with a database available at a primary deployment of the data provider; responsive to the detecting of the replication request, generating a local instance of the database at the remote deployment, the generating of the local instance based on invoking a database refresh operation and pushing database data of the database available at the primary deployment to a database shell at the remote deployment in response to the database refresh

Assignees

Inventors

Classifications

  • G06F16/273Primary

    Asynchronous replication or reconciliation · CPC title

  • Management specifically adapted to replicated file systems · CPC title

  • Query processing · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11989206B2 cover?
Techniques for database replication using replication preparation objects include storing, by at least one hardware processor, at least one task object at a remote deployment of a data provider. A replication request originating from an account of a data consumer is detected at the remote deployment using the at least one task object. The replication request is associated with a database availa…
Who is the assignee on this patent?
Snowflake Inc
What technology area does this patent fall under?
Primary CPC classification G06F16/273. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue May 21 2024 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).