Snowflake Inc.

Microsoft Technology Licensing, LLC

Oracle International Corporation

Other

Subramanian Muralidhar

Benoit Dageville

Thierry Cruanes

Damien Carru

Istvan Cseri

David Schultz

Torsten Walther Grabs

Shreyas Narendra Desai

Khalid Zaman Bijon

Pui Kei Johnston Chu

Di Wu

Sahaj Saini

Nithin Mahesh

Artin Avanes

Saurin Shah

Unmesh Jagtap

Zheng Mi

Nileema Shingte

Eric Robinson

Prasanna V Krishnan

Ganeshan Ramachandran Iyer

German Alberto Gil Echeverri

Vishnu Dutt Paladugu

Sameer Deshpande

Allison Waingold Lee

Durga Mahesh Arikatla

Raja Suresh Krishna Balakrishnan

Muralidhar Krishnaprasad

Jian J Xu

Jeremy Yujui Chen

Chieh-Sheng Wang

Shakhina Pulatova

Anil Kumar Nori

Bowen Zhang

Yujie Li

Robert Bengt Benedikt Gernhardt

Xiaodi Ke

Monica J Holboke

Laxman Mamidi

Polita Paulus

Simon Holm Jensen

Nicola Dan Onose

Vikas Jain

Ryan Michael Thomas Shelly

Brian Smith

Jaeyun Noh

Jiaqi Yan

Tyler Jones

Daniel E Sotolongo

Daniel Mills

James G Pan

Jiaxing Liang

Qin Yu

Abdullah Al Mahmood

Ramachandran Natarajan Iyer

Xin Huang

Raghav Ramachandran

Ravi Murthy

William H Waddington

John Morgan Oslake

Orestis Kostakis

Bhaskar Ghosh

Pablo Castro

Susan M Kotsovolos

Anil Nori

Mikhail Kazhamiaka

Andrew Conrad

Adiel Yoaz

Jeffrey Robert Currier

Richard Shawn Bice

Sean B House

Srinidhi Karthik Bisthavalli Srinivasa

Narayan Nevrekar

Marianne Shaw

Nipun Agarwal

Zhen Hua Liu

Lev Novik

Eric Sedlar

Lik Wong

Namit Jain

Sivasankaran Chandrasekar

James William Stamos

Vikas Arora

Thomas Chang

Tyler Arthur Akidau

James W Warner

Michael Pizzo

Jose A Blakeley

Anand Manikutty

Chris A Suver

Visar Nimani

Yi Fang

Gabriel Kliot

Sudarshan Anand Chitre

Michael Justin Flasko

Mahesh Subramaniam

Lin Chan

Sankara J Subramanian

Hitesh Madan

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

Embodiments of the present disclosure related to sharing applications within a data sharing platform. An example method includes replicating a database from a provider account of a data sharing platform to a consumer account of the data sharing platform. The method further includes executing an installation script within the consumer account to install an application in the consumer account of the data sharing platform responsive to the replicating. The method further includes creating, by a processing device, a set of database roles to manage execution of the application in the consumer account, wherein one or more of the set of database roles determine access privileges granted to the application for accessing the database inside the consumer account. The application is to perform a data processing service relative to a data asset in the database.

Native applications using database roles

Techniques for creating and using error tables to track errors associated with a base table are described. A command to perform an operation on a base table stored in a network-based data system can be received and executed, causing at least one error. At least one error record corresponding to the at least one error can be inputted into an error table, which is nested with the base table. Contextual information can be added to the at least one error record.

Error tables for use with recovery actions

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

Disclosed is an execution information sharing system that writes execution information to a provider target (and other targets) in a secure manner. Execution information generated by an application may be written to a consumer stage, wherein the application is shared by a provider account of a data exchange with a consumer account that executes the application. A consumer exchange service (ES) of the data exchange may send a request to a copy service of the data exchange to copy the execution information from the consumer stage to the provider stage, wherein the consumer ES is a part of the data exchange and is protected from actions of the consumer account. A copy operation may be executed to copy the execution information from the consumer stage to the provider stage using the copy service of the data exchange. The execution information is ingested from the provider stage to a provider table.

Sharing events and other metrics in native applications

A data platform creates an application in a data-provider account, where the application includes one or more application programming interfaces (APIs) corresponding to one or more underlying code blocks. The data platform shares homomorphically encrypted provider data with the application in the data-provider account. The data platform installs, in a data-consumer account, an application instance of the application. The data platform shares homomorphically encrypted consumer data with the application instance in the data-consumer account. The data platform invokes one or more of the APIs of the application instance to execute respective associated underlying code blocks, which are not visible to the data-consumer account, and which operate on the shared homomorphically encrypted provider data and the shared homomorphically encrypted consumer data. The data platform saves homomorphically encrypted output of the one or more respective associated underlying code blocks locally within the data-consumer account.

Data clean rooms using defined access with homomorphic encryption

Techniques for deduplicating files to be ingested by a database are disclosed. A bloom filter may be built for each of a first set of files to be ingested into a data exchange to generate a set of bloom filters, wherein each of the set of bloom filters is built with a number of hash functions that is based on a desired false positive rate. The set of bloom filters may be stored in the metadata storage of the data exchange. In response to receiving a set of candidate files to be ingested, identifying using the set of bloom filters, candidate files from the set of candidate files that are duplicative of a file in the first set of files and pruning from the set of candidate files, each candidate file identified as being duplicative of a file in the first set of files using the set of bloom filters.

Efficient deduplication of randomized file paths

Systems and methods for an organization-level account for an organization on a data platform, users of which can possess administrative or management privileges with respect to the organization and across one or more others accounts of the organization.

Organization-level account on data platform

An anti-abuse system is provided for a data-platform. An anti-abuse scanner of the data-platform detects a creation of an application package by a provider of content to the data platform where the application package includes a set of files for deployment on the data platform. The anti-abuse scanner performs a review o the set of files to detect malicious content where the review is based on a set of analysis rules and generates a deployment decision for the application package based on a result of the review.

Application trust framework

A process of fulfilling a database deployment request for a data platform. A compute service manager of the data platform scans one or more accounts of a consumer region of the data platform for a pending listing fulfillment request, where the pending listing request includes a request for deployment of a consumer database and an associated share of grant metadata of the consumer database within the consumer region. When the compute service manager determines that an account of the one or more accounts has a pending listing fulfillment request, the compute service manager determines a listing for the pending listing fulfillment request based on listing data of the account. The compute service manager determines that no other fulfillment task is scheduled for the pending listing fulfillment request and schedules a background fulfillment task to perform the fulfillment process for the pending listing fulfillment request.

Background job based refresh fulfillment

Techniques for continuous ingestion of files using custom file formats are described. A custom file format may include formats not natively supported by a data system. Unstructured files (e.g., images) may also be considered custom file formats. A custom file format may be set using a user defined table function and scanner options.

Continuous ingestion of custom file formats

A system for data object replication includes at least one hardware processor and at least one memory storing instructions. The instructions cause the at least one hardware processor to perform operations including parsing a replication request to obtain a data object and identification information identifying a set of databases at a first deployment of a data provider. A dependency of the data object to one or more additional data objects stored in the set of databases is detected. A sequential replication of the data object and the one or more additional data object from the first deployment to a second deployment of the data provider is performed. The second deployment is identified by the replication request. A sequence of the sequential replication is based on the detected dependency.

Data object replication using database identification

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

Aspects of the present disclosure address systems, methods, and devices for tracking object dependencies in a cloud database system. An object dependency created between a referencing object and a referenced object is detected. Based on detecting the object dependency, a dependency record is generated. The dependency record includes dependency information describing the object dependency between the reference object and the referenced object. The dependency record is stored in a database of dependency records.

Management of object dependency records in a cloud system

Growing community of inventors

Mercer Island, WA, United States of America

Subramanian Muralidhar