Snowflake Inc.

Shreyas Narendra Desai

Subramanian Muralidhar

Benoit Dageville

Pui Kei Johnston Chu

German Alberto Gil Echeverri

Prasanna V Krishnan

Di Wu

Bowen Zhang

Nithin Mahesh

Sahaj Saini

Eric Robinson

Vishnu Dutt Paladugu

Sameer Deshpande

Damien Carru

Chieh-Sheng Wang

Khondokar Sami Iqram

A system for sub-table replication within a materialized view of a source data table. A materialized view of a source data table is generated based on a query, the source data table having a plurality of data table rows associated with a plurality of client identifiers and including an entitlements column and data content, the entitlements column including a plurality of provider account identifiers and a plurality of consumer account identifiers. An update to an entitlements table of the source data table is detected where the entitlements table includes a plurality of entitlements table rows and where the entitlements table rows are associated with the client identifiers, the consumer account identifiers, and the provider account identifiers. An update to the source data table based on the first update to the entitlements table is detected, and an incremental replication of the materialized view of the source data table is performed.

Materialized view sub-database replication

A method of implementing sub-table replication starts with the processor detecting an update to an entitlements table. The processor performs filtering of a data table based on the update to the entitlements table. The data table including an entitlements column. The processor detects an update to the entitlements column and performs incremental replication of the data table by causing a version-based replication to be executed. Other embodiments are also described herein.

System for list-based database replication

Embodiments of the present disclosure relate to sharing data using database roles. Database roles are generated within a database container of a provider account. Grants to a particular subset of the plurality of data objects of the database container may be assigned to each of the database roles, and each of the database roles are granted to a share object. The share object is mounted within a consumer account to generate an imported copy of each of the database roles. The imported copy of one or more of the database roles is granted to each of one or more account level roles of the consumer account. When a new object is added to a particular database role, it is immediately available for consumption by any account level roles to which the imported copy of the particular database role has been granted.

Fine-grained access control via database roles

Techniques for database replication include a method performed by at least one hardware processor of a resource management node. The method includes detecting a request that a database instance of a database stored at a first network deployment is available at a second network deployment. Responsive to the request, the second network deployment is provisioned with a plurality of data objects. A first data object of the plurality of data objects includes a database shell. The database shell is reconfigured as the database instance of the database based on pushing data of the database into the database shell. Access to the database instance at the second network deployment is authorized based on at least a second data object of the plurality of data objects.

Database replication using a resource management node

A database system can configure network devices, such as a primary database in a multi-tenant deployment and a secondary database in a private deployment, to send and receive sequence messages, such as input data indicative of a selection of a link. The database system can create a secure share area in the private deployment in response to receiving the input data indicative of the selection of the link. The database system can replicate the data from the multi-tenant deployment to the secure share area in the private deployment and share the replicated data from the secure share area to the secondary database hosted in the private deployment.

Managing database traffic between isolated database systems

Various embodiments provide for replicating a share across deployments of a data platform, where the share can be on a source deployment and the share can be replicated on one or more target deployments, and where the share is replicated with one or more database objects of the source deployment associated with the share. Some embodiments analyze the share to be replicated and, based on the analysis, determine one or more database objects that would be replicated to the one or more target deployments to enable a replica of the share on the one or more target deployments.

Replication of share across deployments in database system

Techniques for database replication for a remote deployment include a method performed by a data platform executing instructions on at least one hardware processor. The method includes detecting receipt of a database replication request associated with a data consumer. The database replication request is requesting availability of an instance of a primary deployment database at a remote deployment of a data platform. In response to detecting the receipt of the database replication request, an account of a data provider at the remote deployment of the data platform is provisioned with a set of replication-preparation objects associated with the primary deployment database. A database refresh operation is invoked, causing database data be pushed from the primary deployment database to a database shell in the account of the data provider at the remote deployment, to create the instance of the primary deployment database.

Database replication for a remote deployment

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.

Automated database replication using replication preparation objects

Provided herein are systems and methods for replicating share objects to remote deployments. An example method includes generating, at a second deployment in a data exchange, a replica of a share object included in a first deployment of the data exchange. The share object grants privileges to a first account to access a first database of the first deployment, wherein the first database comprises a database object. The method also includes retrieving, at the first deployment, share grant metadata from the share object of the first deployment, wherein the share grant metadata includes a reference to the database object and allows the first account to use the database object. The method also includes transmitting a message comprising the share grant metadata to the replica in the second deployment. The share grant metadata in the replica allows a second account to use the database object replicated in the second deployment.

Share replication between remote deployments

A network device communication system can configure network devices, such as a first database in a multi-tenant deployment and a second database in a private deployment, to send and receive sequence messages, such as replication data, over a channel comprising a plurality of private network nodes. The first database can create a link specifying the data share and the second database. The second database selects the link and a secure area in the private deployment is created into which data is replicated and shared with further accounts in a computationally secure and efficient manner.

Database sharing in a virtual private deployment

System for regional database replication

Embodiments of the present disclosure relate to sharing database roles using hidden roles. A database role may be generated within a database container having a plurality of data objects, wherein the database role exists exclusively within the database container. A set of grants to a particular subset of the plurality of data objects of the database container may be assigned to the database role and the database role may be granted to the share object. The share object is mounted within a consumer account to generate an imported database container within the consumer account, the imported database container including an imported copy of the database role. The imported copy of the database role may be granted to each of one or more account level roles of the consumer account to share the particular subset of the plurality of data objects without creating proxy objects in the consumer account that represent the particular subset of the plurality of data objects.

Growing community of inventors

Bellevue, WA, United States of America

Shreyas Narendra Desai