Merge pull request #5 from lapate/SQLMod

Updated contents with typo fixes and match to master template

043-SQLModernization/Coach/Solution02.md

@@ -4,59 +4,60 @@
 
 ## Notes & Guidance
 
-This optional challenge focuses on performing On-prem SQL Server migration to SQL Server on Azure VM (IaaS). The challenge involves step by step approach on managing the migreation using new capabilities of "Azure Migrate". The new capabilities includes creation of migration project with two main phases. Phase 1 is discvery and assessment, whle phase 2 is using the assessment recommendtions to perform actuall migration of the VM.   
+This optional challenge focuses on performing On-prem SQL Server migration to SQL Server on Azure VM (IaaS). The challenge involves step by step approach on managing the migration using new capabilities of "Azure Migrate". The new capabilities include creation of migration project with two main phases. Phase 1 is discovery and assessment, while phase 2 is using the assessment recommendations to perform actual migration of the VM.   
 
-Although this challenge only includes migrating from SQL Server VM to IaaS, the new capabilities inlcude migrating from SQL Server VM to Azure SQL DB (PaaS). Please refer to additional documentation -  https://docs.microsoft.com/en-us/azure/migrate/how-to-create-azure-sql-assessment.
+Although this challenge only includes migrating from SQL Server VM to IaaS, the new capabilities include migrating from SQL Server VM to Azure SQL DB (PaaS). Please refer to additional documentation -  https://docs.microsoft.com/en-us/azure/migrate/how-to-create-azure-sql-assessment.
 
 ### Environment Setup
 
-The challenge environment steup includes creating a Azure SQL Server VM in a source virtual network to mimic on premises scenario.  The SSQL Server VM will be in Virtual Network and have the HammerDB (SQL trafic benchmarking tool) running on it. The tool could be downloaded from here - https://www.hammerdb.com/HammerDB. The tool will continuously generate the traffic for 'n' virtual users to mimic the real life sceanrio. The HammerDB is a handy tool to not only build the database but also generate the traffic patterns, The assement phase of the challenge takes this traffic pattern into consideration, while recommending the right solution.
+The challenge environment setup includes creating a Azure SQL Server VM in a source virtual network to mimic on premises scenario.  The SQL Server VM will be in Virtual Network and have the HammerDB (SQL traffic benchmarking tool) running on it. The tool could be downloaded from here - https://www.hammerdb.com/HammerDB. The tool will continuously generate the traffic for 'n' virtual users to mimic the real life scenario. The HammerDB is a handy tool to not only build the database but also generate the traffic patterns, The assessment phase of the challenge takes this traffic pattern into consideration, while recommending the right solution.
 
 ![Generated Traffic](./images/hammerDB-VirtualUser-traffic.png)
 
-### Discovery and Assement 
+### Discovery and Assessment 
 
 1. Login to Azure Portal and create a Resource Group, to host subsequent resources as described below.
 2. Create Azure Migrate Project. https://docs.microsoft.com/en-us/azure/migrate/tutorial-discover-physical#set-up-a-project
 
 3. Setup Discovery Appliance. 
     - Create/Deploy Windows Server 2016 (Datacenter) VM.
 
-    - RDP to the VM as an administrator and download the AzureMIgrateINstallerServer-Public. 
+    - RDP to the VM as an administrator and download the AzureMigrateINstallerServer-Public. 
 
     - Login to Azure Portal and navigate to "Azure Migrate". If the previously created project is not selected   
-      select it on tghe top right corner.
+      select it on the top right corner.
 
-    - Under "Windows, Linux and SQL Server" -> Assement tools -> Click "Discover". This will take you to setup   
+    - Under "Windows, Linux and SQL Server" -> Assessment tools -> Click "Discover". This will take you to setup   
       screen for discover appliance.
 
     - Select the "Physical or other (AWS, GCP, Xen etc." dropdown option for "Are your servers virtualized?".  
 
-    - Generate project key, by giving a appliance name and keep it handy. It wil be required when associating the 
+    - Generate project key, by giving a appliance name and keep it handy. It will be required when associating the 
       appliance with Azure migrate project. 
 
     - Download and extract the "Azure Migrate Appliance". Navigate to the folder where extracted
-    - Open a powershell session and run the Azure migrate installer script - .\AzureMigrateInstaller.ps1.
+
+    - Open a Powershell session and run the Azure migrate installer script - .\AzureMigrateInstaller.ps1.
 
       ![Discovery Appliance installer](./images/azmigratediscoveryinstaller.png)
 
-4. Verify Appliance can access the public URLs
+4. Verify that the Appliance can access the public URLs
     - Ensure windows firewall is allowing outbound traffic to Azure.
 
-5. Configure the applicance
-    - Navigate to the URL - https://<appliancename>:44368
-    - Let the step 1 Set up prerequisite finish.
+5. Configure the appliance
+    - Navigate to the URL - https://appliancename:44368
+    - Let the step 1 of the set up prerequisite finish.
 
       ![Discovery Appliance configuration 1](./images/azmigratediscoveryinstallersetup1.png)
 
-    - Register the appliance with Azure migrate by loginingin. The key "Project key" obtained in step above will 
+    - Register the appliance with Azure migrate by logging in. The key "Project key" obtained in step above will 
       be validated automatically.
 
       ![Discovery Appliance configuration 2](./images/azmigratediscoveryinstallersetup2.png)
 
 6. Start continuous discovery.
 
-    - Add Credentials. This are the default server login admin crdeentials (one used during VM creation)
+    - Add Credentials. This is the default server login admin credentials (one used during VM creation)
 
       ![Add Credentials](./images/azmigratediscoveryinstallersetup3credentials.png)
 
@@ -79,16 +80,16 @@ The challenge environment steup includes creating a Azure SQL Server VM in a sou
 
     ![Create Assessment](./images/azmigratediscoveryiassessment1.png)
 
-    - Assements are organized by groups. You could run multiple assemenst if needed. Everytime you create a new 
-      assessment , newly collected metric data is used for the recommendations that are generated. In production scenarios, it is recommended that you let the discovery run for few days, before creating an assessment.
+    - Assessments are organized by groups. You could run multiple assessment if needed. Every time you create a new 
+      assessment, newly collected metric data is used for the recommendations that are generated. In production scenarios, it is recommended that you let the discovery run for few days, before creating an assessment.
 
     ![Create Assessment group](./images/azmigratediscoveryiassessment2.png)
 
-    - Review assements and if required export it.
+    - Review assessments and if required export it.
 
     ![Create Assessment export](./images/azmigratediscoveryiassessmentreview1.png)
 
-    - Check on the exported assement.
+    - Check on the exported assessment.
 
     ![View Assessment](./images/azmigratediscoveryiassessmentexported.png)
 
@@ -106,10 +107,10 @@ The challenge environment steup includes creating a Azure SQL Server VM in a sou
     - Create/Deploy Windows Server 2016 (Datacenter) VM, within previously created "source" resource group. In 
       addition create a target resource group with Virtual network created in it. We'll use the "default" subnet in this target Virtual network as our landing spot for migrated SQL server VM. Lets call this a "target" resource group. 
 
-    - Add a new data disk to the VM (1TB), which will be used by the repliacation agent (ASR agent). Mde details 
+    - Add a new data disk to the VM (1TB), which will be used by the replication agent (ASR agent). More details 
       below.
 
-    - RDP to the VM as an administrator and ensure the newly attached data disk is attached and active nby 
+    - RDP to the VM as an administrator and ensure the newly attached data disk is attached and active by 
       configuring it in the "disk management" system utility. A new volume letter is allocated for this new volume. This volume is used latter during the installation process.
 
     - Login to Azure Portal and navigate to "Azure Migrate". If the previously created project is not selected select it on the top right corner.
@@ -122,9 +123,9 @@ The challenge environment steup includes creating a Azure SQL Server VM in a sou
 
     - Select the "Install a replication appliance" dropdown option for "do you want to install a new replication appliance or scale out existing setup".
 
-    - Download the replication appliance software (AzureSiteREcoveryUnifiedSetup.exe) and the registration key file. Run the setup and select the downloaded "registration key" in the wizzard. For install path, select the newly attached datadisk volume.
+    - Download the replication appliance software (AzureSiteREcoveryUnifiedSetup.exe) and the registration key file. Run the setup and select the downloaded "registration key" in the wizzard. For install path, select the newly attached data disk volume.
 
-    - Once the installation completess, validate that the "hostconfigwxcommon" and "cspsconfigtool" shortcuts are seen on the desktop. These are the programs to setup configuration and process server.
+    - Once the installation is completed, validate that the "hostconfigwxcommon" and "cspsconfigtool" shortcuts are seen on the desktop. These are the programs to setup configuration and process server.
 
     - Open "cspsconfigtool" and add a new account to be used for replication. Ensure this is the local account on the target machine.
 
@@ -139,8 +140,8 @@ The challenge environment steup includes creating a Azure SQL Server VM in a sou
     ![Configuration Server - ASR registration](./images/azmigrateConfiurationServerSetup3.png)
 
 
-3. Setup Moblity Service
-    - Before replication could start, the mobility service agent must be installed on the source SQL Server machine that needs to be replicated. This is required for non-virtualized VMs which are on-premises or in other clouds (GCP, AWS). PLease refer to this link for details - https://docs.microsoft.com/en-us/azure/migrate/tutorial-migrate-physical-virtual-machines#install-the-mobility-service.
+3. Setup Mobility Service
+    - Before replication could start, the mobility service agent must be installed on the source SQL Server machine that needs to be replicated. This is required for non-virtualized VMs which are on-premises or in other clouds (GCP, AWS). Please refer to this link for details - https://docs.microsoft.com/en-us/azure/migrate/tutorial-migrate-physical-virtual-machines#install-the-mobility-service.
 
       Follow the instructions on the link and start the installation on the source SQL Server VM.
 
@@ -160,17 +161,17 @@ The challenge environment steup includes creating a Azure SQL Server VM in a sou
 
 4. Start replication.
 
-    - Login to Azure Portal and navigate to "Azure Migrate". If the previously created project is not selected select it on tghe top right corner.
+    - Login to Azure Portal and navigate to "Azure Migrate". If the previously created project is not selected select it on the top right corner.
 
-    - Under "Windows, Linux and SQL Server" -> Migration tools -> Click "Replicate". This will take you to setup screen to bgin replication. RUn through the wizzard by selecting the source settings. Select the previously created replication appliance and the user account that was created in the previous step. Click Next.
+    - Under "Windows, Linux and SQL Server" -> Migration tools -> Click "Replicate". This will take you to setup screen to begin replication. Run through the wizard by selecting the source settings. Select the previously created replication appliance and the user account that was created in the previous step. Click Next.
 
     ![Replicate - start](./images/azmigrateReplicate1.png)
 
     - Select the virtual machine that was discovered in the discovery step. You could select multiple of them in production scenario. Click Next
 
     ![Replicate - select VM](./images/azmigrateReplicate2.png)
 
-    - Select the target environmet settings. This includes target subscription, resource group, virtual network and subnet. The migrated SQL Server VM will be landing here. Click Next.
+    - Select the target environment settings. This includes target subscription, resource group, virtual network and subnet. The migrated SQL Server VM will be landing here. Click Next.
 
     ![Replicate - select target env](./images/azmigrateReplicate3.png)
 
@@ -182,7 +183,7 @@ The challenge environment steup includes creating a Azure SQL Server VM in a sou
 
     ![Replicate - select target disks](./images/azmigrateReplicate5.png)
 
-    - Review ans start replication. This action will initiate a job to replicate the VM. Wait for the job to finish typically it takes 8-10 hrs. for completion.
+    - Review and start replication. This action will initiate a job to replicate the VM. Wait for the job to finish typically it takes 8-10 hrs. for completion.
 
     ![Replicate - start replication](./images/azmigrateReplicate6.png)
 
@@ -195,7 +196,7 @@ The challenge environment steup includes creating a Azure SQL Server VM in a sou
     ![Replicate - review topology](./images/azmigrateReplicate8.png)
 
 
-5. Before you initiate migration, it is a best practice to test it. Test MIgration allows to test the replicated server failover and uncover any issues. 
+5. Before you initiate migration, it is a best practice to test it. Test Migration allows to test the replicated server failover and uncover any issues. 
     - Start Test migration.
 
     ![Start Test](./images/azmigratestarttest.png)
@@ -209,7 +210,7 @@ The challenge environment steup includes creating a Azure SQL Server VM in a sou
     ![Validate Test](./images/azmigrateendtest.png)
 
 
-6. Now that the tesing is complete proceed with actual Migration of the VM to the target resource group
+6. Now that the testing is complete proceed with actual Migration of the VM to the target resource group
     - Start Migration.
 
     ![Start Migration](./images/azmigratestartmigrate.png)
@@ -219,7 +220,7 @@ The challenge environment steup includes creating a Azure SQL Server VM in a sou
     ![Validate Migration](./images/azmigrateendmigrate.png)
 
 
-7. Congratulations!! At this point you have successfully migrated an on-prem VM to Azure using the Azure migrate automation and took advantage of the scale and Machine learning based migration reccomndations. Validate migrated VM in the target resource group by logging into the VM and see the databases. Left is source and right is the migrated target VM below
+7. Congratulations!! At this point you have successfully migrated an on-prem VM to Azure using the Azure migrate automation and took advantage of the scale and Machine learning based migration recomendations. Validate migrated VM in the target resource group by logging into the VM and see the databases. Left is source and right is the migrated target VM below
 
     ![Successful completion](./images/azmigratefinalvalidation.png)
 

043-SQLModernization/Student/Challenge02.md

@@ -10,8 +10,6 @@ Your team is wondering what options are available to leverage automation for the
 
 The objective of this challenge is to migrate TPCC (benchmark database - http://www.tpc.org/tpcc/) to Azure. The TPCC database is used as a benchmark for a typical OLTP workloads. 
 
-### Challenge details 
-
 Your company has provided the following requirements and guidelines:
 
 1. Must take advantage of latest automation tools available to execute migration at scale.