Best Practices for Data Consumers

This topic provides context on how data managed from the Revenera side is shared through Snowflake’s data share mechanism, and how this aligns with industry standard practice of using Snowflake data shares between data providers and their consumers.

•

Revenera shares customer data using Snowflake Secure Data Sharing through secure views, which is Snowflake’s intended and recommended mechanism for governed, cross-account data access. Secure views allow us to provide strong isolation, governance, and privacy controls while maintaining a single, authoritative definition of the shared data.

Tip:For details, see the Snowflake documentation: Use secure objects to control data access.

•

Revenera publishes a standardized set of secure views that expose raw, governed datasets consistently across all customers. This approach follows Snowflake’s zero-copy sharing model, where the data provider maintains one canonical view definition, and data consumers apply their own transformations, filters, joins, or column exclusions within their own Snowflake accounts as needed.

Tip:For details, see the Snowflake documentation: About Secure Data Sharing.

•

In line with Snowflake’s Secure Data Sharing architecture and common industry best practices, customer-specific customizations on shared views such as hiding or removing columns for individual consumers are not supported. Creating separate customized views for each customer would significantly increase long-term maintenance overhead, fragment the shared schema, and shift data modeling responsibilities from the consumer to the data provider. These also introduce tighter operational dependencies, which goes against the design principles of scalable data sharing and data democratization.

•

The recommended approach for consumers is to manage any consumer-specific requirements within their own Snowflake environment. This typically includes:

•

Selecting only the required columns in their queries

•

Creating local views or derived tables within their own Snowflake account

•

Applying customer-specific transformations or business logic independently

This model ensures loose coupling between the data provider and consumers, improves scalability, and allows each consumer to tailor the data to their needs without introducing long-term operational dependencies.

Revenera will:

•

Share complete datasets via secure views

•

Maintain strong governance, privacy, and consistency across customers

•

Receive any feedback from producers on missing data elements from the shared secure views, and act on those after internal review