This end-to-end and step-by-step quick demo shows you how to connect an existing on-premises data source to a modern cloud data warehouse solution such as Snowflake:
Easily
Fast
Securely, and
Without having to write a single line of code.
Table of Contents
Furthermore, it demonstrates that Snowflake on Azure is a great combination of the Azure data factory, Azure functions and Microsoft Power BI, besides other well-known connected services in the Azure cloud ecosystem, including the single sign-on feature with the Azure active directory. It also shows that it is possible to build a hyper-scale enterprise data analytics solution with a dual vendor strategy.
The Azure data factory can perform both, ELT and ETL tasks. Currently, there is no native Snowflake open source connector available in ADF V2. However, with the Snowflake.net Driver several options are possible for workloads with Azure functions and custom activities, together with Azure data factory pipelines.
Scenarios depend on many factors and circumstances. In our case, the sources are mostly relational database management systems. For several reasons, we do not want to extract data from our source system to a csv file, and then transfer the csv to cloud blob storage and load these into Snowflake with native connectors. However, this would still be a highly valid and common scenario.
We want to go for a scenario where we have directly linked both databases, using the Azure data factory to load the data directly from the source tables into Snowflake tables. After loading the data, we want to use Microsoft Power BI to analyze the data with a live connection to the analytics model. This direct connection to the data warehouse has the advantage that we do not need to reload the data out of Snowflake.
Tools and services used for the demo:
SQL Server 2017 database, on-premises
Azure runtime integration, on-premises
Azure data factory V2 pipeline (integration runtime configured)
Snowflake data warehouse
Power BI
Background: Architecture on Azure – how we built it:
Open ODBC data sources (64-bit) and create a new data source
Enter the details into the Snowflake connection dialog
Install and configure Azure integration runtime
Create and configure integration runtime in an Azure data factory V2
Installieren Sie Azure Runtime-Integration, intern (On-Premises)
Register the runtime and enter the authentication key from the ADF V2 runtime created earlier
Create a new ODBC-linked service in the Azure data factory
Configure the ODBC-linked service by entering the data source name, user name, and password created earlier
Test the connection from the Azure data factory
Create a table in Snowflake
Data types are irrelevant in this quick demo.
Grant proper access rights, in case they are needed. For this demo, we do it quickly, which is normally not recommended:
Copy the data wizard from the Azure data factory V2
Source SQL server 2017, on-premises
Create a new linked service to an on-premises SQL server. Any linked service that supports Azure integration runtime is available here, including Oracle, Sap, MySQL, Teradata, etc. Or you can connect easily to Snowflake with a direct load through the Azure data factory.
Enter the server name, reached through the previously configured Azure integration runtime, and get authenticated. Test the connection.
Now select the recently configured on-premises data source.
Select your data tables from your on-premises data source
Select the Snowflake linked service created earlier as the destination
Map the selected tables
Map the columns between the tables
Settings
Summary
Let the pipeline run
Connect with the Power BI direct query
Conclusion
Connect quickly and easily to almost any on-premises data source – without having to write any line of code, whatsoever.
Although it may not appear as such, the warehouse size does have a measurable impact on ETL/ ELT workloads on reporting workloads. This means the concept of using different warehouse sizes for different workloads or user groups makes absolute sense.
Currently, there is no native Snowflake connector available in ADF V2, but there is a .net driver that can be used to create your own.
The demo showed that Snowflake on Azure is a great combination of the Azure data factory, Azure functions and Microsoft Power BI, besides other well-known connected services in the Azure cloud ecosystem, including the single sign-on feature with the Azure active directory. It also shows that it is possible to build a hyper-scale enterprise data analytics solution with a dual vendor strategy.
Larger data volumes could take longer to transfer, depending on various factors.
Who is b.telligent?
Do you want to replace the IoT core with a multi-cloud solution and utilise the benefits of other IoT services from Azure or Amazon Web Services? Then get in touch with us and we will support you in the implementation with our expertise and the b.telligent partner network.
Exasol is a leading manufacturer of analytical database systems. Its core product is a high-performance, in-memory, parallel processing software specifically designed for the rapid analysis of data. It normally processes SQL statements sequentially in an SQL script. But how can you execute several statements simultaneously? Using the simple script contained in this blog post, we show you how.
Many companies with SAP source systems are familiar with this challenge: They want to integrate their data into an Azure data lake in order to process them there with data from other source systems and applications for reporting and advanced analytics. The new SAP notice on use of the SAP ODP framework has also raised questions among b.telligent's customers. This blog post presents three good approaches to data integration (into Microsoft's Azure cloud) which we recommend at b.telligent and which are supported by SAP.
First of all, let us summarize the customers' requirements. In most cases, enterprises want to integrate their SAP data into a data lake in order to process them further in big-data scenarios and for advanced analytics (usually also in combination with data from other source systems).
As part of their current modernization and digitization initiatives, many companies are deciding to move their data warehouse (DWH) or data platform to the cloud. This article discusses from a technical/organizational perspective which aspects areof particularly important for this and which strategies help to minimize anyrisks. Migration should not be seen as a purely technical exercise. "Soft" factors and business use-cases have a much higher impact.