page262
349
Setting the Standard
Having discussed entitling your data products, let’s discuss how you can set the standard
for distributing your data products. I will not discuss this in great depth but will call out
some available options.
Imported Database Entitlement
Imported databases created from shares or replicated databases do not import source
provider entitlement. By now you should all be familiar with role-based access control
(RBAC), you should provision a sample RBAC script segregating your shared objects
into data products for your client to begin integrating your data products with their local
data sets.
The sample RBAC should be accompanied by a data model and data catalog.
Sample SQL for Common Use Cases
Regardless of whether your application has implemented embedded entitlement or
pre-filtered entitlement, you should provision a suite of SQL statements. These SQL
statements should implement common use cases and act as a starting point for your
clients by demonstrating how to extract business value from the data product.
A suite of tuned, performant example SQL statements will help remediate client
performance issues by demonstrating both functional and performant Snowflake
interaction. You must remember that the Snowflake optimizer functions differently than
legacy relational database management systems (RDBMSs). Therefore, your sample SQL
statements will also serve as a guide to uplift your client skills.
Client Collaboration
Many clients use your organization’s data products in conjunction with both your
competitor data products and their own internal data products. Joining across imported
schemas where embedded entitlement logic exists in third-party data sets is highly likely
to result in performance issues.
I advise caution. Before purchasing a third-party data set, I suggest you fullly
understand all of the underlying query object implementations.
Chapter 9
Client expeCtations