Skip to content

Latest commit

 

History

History
83 lines (53 loc) · 5.07 KB

File metadata and controls

83 lines (53 loc) · 5.07 KB

Challenge 0 -- Setup

Next Challenge>

Description

The objective of this lab is to setup your on-premise data warehouse environment for the hack. This will be your reference point for the migration.

Success Criteria

  1. Complete setup of your environment
  2. Determine which SQL database offering is the best fit for the hack
  3. Estimate the size of your environment and the overall # of compute and storage nodes (No precision just concepts)

Learning Resources

  1. Decision Tree for Analytics
  2. DWU Units
  3. Capacity Settings
  4. Capacity Limits SQL Dedicated Pools
  5. Synapse Analytics Best Practices & Field Guidance
  6. Azure Synapse Analytics Migration Guides
  7. Reference Architecture for Lambda Big Data Platforms

Pre-requisites

  1. Laptop computer as Development environment
  2. Azure Subscription

Setup your Development Environment on your Laptop

  1. SQL Server Management Studion (Version 18.x or higher)
  2. Visual Studio Code
  3. Power BI Desktop

Setup Azure Tenant with Services for What the Hack

WWI runs their existing database platforms on-premise with SQL Server 2017. There are two databases samples for WWI. The first one is for their Line of Business application (OLTP) and the second is for their data warehouse (OLAP). You will need to setup both environments as our starting point in the migration.

  1. Open your browser and login to your Azure Tenant. We plan to setup the Azure Services required for the What the Hack (WTH). In your portal, open the Azure Cloud Shell

  2. Go into the cloud shell and select the subscription you plan to use for this WTH.

az account set --subscription {"Subscription Name"}
az account show
  1. Create a resource group to store the Modern Data Warehouse What the Hack. This will be the services for your source systems/environments. In Cloudshell, run this command
az group create --location eastus2 --name {"Resource Group Name"}
  1. In the Cloudshell, run this command to create a SQL Server instance and restore the databases. This will create an Azure Container Instance and restore the WideWorldImporters and WideWorldImoprtersDW databases. These two databases are your LOB databases for this hack.
az container create -g {Resource Group Name} --name mdwhackdb --image alexk002/sqlserver2019_demo:1  --cpu 2 --memory 7 --ports 1433 --ip-address Public
  1. At the start of Challenge 1, reach out to your coach and they will share username and password for the LOB databases for this hack.

  2. Upload your ARM templates into Azure CloudShell.

    /Student/Challenges/Challenge0/ARM.
    The files are parametersFile.json and template.json. Edit the parmeters file and replace any {} with information requested.

  3. Run the last command to setup Azure Data Factory, Azure SQL Server Instance and SSIS Runtime. This will build out for Challenge 1 the SSIS environment in Azure Data Factory.

az deployment group create --name final --resource-group {ENTER RESOURCE GROUP NAME} --template-file template.json --parameters parametersFile.json
  1. Last step is to start your Azure Data Factory SSIS Runtime Service. Go to Connection pane in your Azure Data Factory service. The startup time is approximately 5 minutes.

  2. Review the database catalog on the data warehouse for familiarity of the schema Reference document

  3. Review ETL workflow to understand the data flow and architecture Reference document

On-premise Architecture

The Solution diagram is described in the text following this diagram.