This document discusses architectures for using Snowflake and Power BI together. It begins by describing the benefits of each technology. It then outlines several architectural scenarios for connecting Snowflake to Power BI, including using a Power BI gateway, without a gateway, and connecting to Analysis Services. The document also provides examples of usage scenarios and developer best practices. It concludes with a section on data governance considerations for architectures with and without a Power BI gateway.
Report
Share
Report
Share
1 of 21
More Related Content
Snowflake + Power BI: Cloud Analytics for Everyone
11. Power BI Delivery Approaches
Business-Led
Self-Service BI
Bottom-Up Approach
IT-Managed
Self-Service BI
Blended Approach
Corporate BI
Top-Down Approach
Analysis using any type of
data source; emphasis on
data exploration and
freedom to innovate
Ownership:
Business supports all
elements of the solution
Scope of Power BI use
by business users:
Data preparation, data
modeling, report creation
& execution
Governed by:
Business
A “managed” approach
wherein reporting utilizes
only predefined/governed
data sources
Ownership:
IT: data + semantic layer
Business: reports
Scope of Power BI use
by business users:
Creation of reports and
dashboards
Governed by:
IT: data + semantic layer
Business: reports
Utilization of reports and
dashboards published by
IT for business users to
consume
Ownership:
IT supports all elements
of the solution
Scope of Power BI use
by business users:
Execution of
published reports
Governed by:
IT
Ownership Transfer
Over time, certain self-service solutions deemed as critical to the business may transfer ownership
and maintenance to IT. It’s also possible for business users to adopt a prototype created by IT.
15. ANALYTICS ARCH W/ GATEWAY
Pros
Better governance on service accounts used
Dedicated resources for scheduled refresh or direct
query
Control refresh or direct query performance
Low cost per node
Cons
Additional maintenance of Gateway Cluster
Workspace contributors or higher need access to
Gateway Data Sources
17. ANALYTICS ARCH WITHOUT GATEWAY
Pros
No infrastructure dependency
Less steps to deploy new datasets
Zero resource cost to integrate
Share datasets across workspaces
Cons
Cannot enforce credentials used by datasets
Can introduce inconsistent deployments leading to:
Dataset sprawl
Unauthorized access
Varying Terminology for the same metrics
19. ANALYTICS ARCH W/ ANALYSIS SERVICES
Pros
Best performance possible
Shared dataset across any workspaces
Gets around the 1GB / file limitation
Cons
Relies on AAD and/or AD
Need to learn Visual Studio
Different UI
Different deployment process
Need to learn Analysis Services
Performance best practices
Processing options
Monitoring and Maintenance
20. DEVELOPER BEST PRACTICES
Make sure you are Query Folding (pushing down Native queries)
Create DATE dimension in Snowflake with Fiscal Calendar
If report is in Direct Query, double-check the Scheduled Cache Refresh Setting is set to Weekly or Monthly. Otherwise YOU
WILL GET CHARGED!
Use Certification process in Power BI for Certified Datasets