Snowflake Inc.

Pui Kei Johnston Chu

Benoit Dageville

Prasanna V Krishnan

Justin Langseth

Matthew J Glickman

Christian Kleinerman

Subramanian Muralidhar

Shreyas Narendra Desai

German Alberto Gil Echeverri

Damien Carru

Bowen Zhang

Di Wu

Nithin Mahesh

Sahaj Saini

Eric Robinson

Vishnu Dutt Paladugu

Jeremy Yujui Chen

Sameer Deshpande

Unmesh Jagtap

Chao Ren

Edmond T Chan

Dangfu Wang

Stephanie Stillman

Thierry Cruanes

Istvan Cseri

Chieh-Sheng Wang

James G Pan

Xiaodi Ke

Steven Parkes

Xie Xu

Tyson J Hamilton

Scott C Gray

Haroldo Level

Khondokar Sami Iqram

Elkhan Mammedov

Rongpeng Zheng

Systems and methods for managing membership in a private data exchange are provided herein. In one embodiment, the method includes creating, in a first data exchange belonging to a first data provider, a first listing. The method further comprises creating, in a second data exchange belonging to a second data provider, a second listing, the second listing comprising a tunnel to the first listing. The method also includes generating, in the second data exchange, a third listing, the third listing comprising data from the second listing and additional data from the second data provider.

Managing version sharing in a data exchange

Sharing data in a data exchange across multiple cloud computing platforms and/or cloud computing platform regions is described. An example computer-implemented method can include creating a listing in a data exchange, the listing including a data set hosted by a first cloud computing entity. The data set can be shared with a second cloud computing entity. The method further includes receiving a request associated with a customer account of the second cloud computing entity to access the data set of the listing hosted by the first cloud computing entity and replicating at least a subset of the data set of the listing from the first cloud computing entity to a provider account at the second cloud computing entity to be accessible by the customer account at the second cloud computing entity.

Creating a global data sharing listing

Provided herein are systems and methods for providing a secure and efficient way to manage a data exchange's availability and manage the visibility of data listings of the data exchange. For example, the method may comprise specifying, by an exchange admin of the data exchange, a set of regions where the data exchange is available, each of the set of regions comprising one or more remote deployments. The method may further comprise specifying by a data provider, one or more of the set of regions where a data listing owned by the data provider is visible. Upon receiving a request to access the data listing from a remote deployment of the one or more regions, the data provider may determine whether to reject or fulfill the request. In response to determining that the request should be fulfilled, replicating data of the data listing to the remote deployment.

Data exchange availability, listing visibility, and listing fulfillment

Sharing data in a data exchange across multiple cloud computing platforms is described. An example method can include copying, to a first cloud computing entity using a consumer account of the first cloud computing entity, a first subset of a data set associated with a provider account of a second cloud computing entity, wherein the provider account of the second cloud computing entity does not have access to the first cloud computing entity, and then copying, to a third cloud computing entity using a consumer account of the third cloud computing entity, a second subset of the data set, wherein the provider account of the third cloud computing entity does not have access to the first cloud computing entity, for which the first subset of the data set is different from the second subset of the data set.

System and method for global data sharing

A method includes creating, by a first provider, a first listing referencing first shared data and comprising first access controls, wherein access to the first shared data by a second provider is filtered based on the first access controls, creating, by the second provider, a second listing referencing second shared data and the first shared data filtered based on the first access controls, and adding the second listing to a catalog in a data exchange, the catalog comprising metadata describing the second shared data.

Accessing listings in a data exchange

Systems and methods for managing membership in a private data exchange are provided herein. In one embodiment, the method includes receiving a request for access to a first listing of a data exchange, each listing of the data exchange comprising version metadata. The method further includes, in response to the request, accessing a first version of a data set referenced by the first listing, wherein the first version of the data set comprises a first structure defined by first version metadata, a second listing of the data exchange references a second version of the data set, the second version of the data set comprising a second structure defined by second version metadata, and the second structure is incompatible with the first structure.

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

Systems and methods for managing membership in a private data exchange are provided herein. In one embodiment, the method includes generating a plurality of listings in a data exchange, each of the plurality of listings comprising version metadata and referencing a data set within a database. The method further includes receiving a request for access to a first listing of the plurality of listings and, in response to the request, accessing a first version of the data set that is compatible with first version metadata of the first listing.

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 regional database replication

Provided herein are systems and methods to provide a way to share metrics regarding shared data access and accesses associated with data providers for different data listings of the data exchange. For example, the method may comprise detecting one or more client interactions with a set of data listings of a data exchange, the set of data listings associated with one or data providers. The method may further comprise collecting metrics corresponding to the one or more client interactions. In addition, the method may share metrics relevant to the one or more data providers with the one or more data providers.

Sharing of data share metrics to customers

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.

Fine-grained access control via database roles

A consumer account may invoke an operation referencing a set of shared objects stored within a database of a provider account using an imported database that makes the set of shared objects available within the consumer account. A call context of the operation may be updated to cache the imported database, which references a share created from the provider account database, the share having grants to the set of shared objects. One or more database level objects may be discovered in a context of the share and each role granted to the share may be obtained based on the one or more database level objects. Whether any role granted to the share has access to any of the set of shared objects may be determined and the operation may be executed for each of the set of shared objects to which any role granted to the share has access.

Shared object discovery techniques

Disclosed is an execution information sharing system that duplicates execution information to a provider target (and other targets) as it is being loaded to a consumer target. A consumer account of a data sharing platform executes an application shared with it by a provider account of the platform. Consumer and provider configurations indicating consumer and provider targets respectively are generated. The consumer configuration and provider configurations are provided to an event context to generate a first and second event unloaders respectively, wherein the event context maintains a mapping linking both the first event unloader and the second event unloader to the application. In response to receiving execution information from the application, the first event unloader and the second event unloader are retrieved. The execution information is then written to the consumer target and the provider target using the first event unloader and the second event unloader respectively.

Sharing events and other metrics in native applications

Methodologies for upgrading and patching an in-database application package and its application instances. A data platform determines a number of objects of an application instance running on the data platform at a previous version level of an application package of the application instance. In response to determining the number of objects of the application package running on the data platform at the previous version level of the application package is one or more, the data platform continues determining the number of objects running on the data platform at a previous version level of the application package. In response to determining the number of objects of the application instance running on the data platform at the previous version level of the application package is none, the data platform upgrades the application instance to the new version of the application package.

Growing community of inventors

San Mateo, CA, United States of America

Pui Kei Johnston Chu