Skip to content

Latest commit

 

History

History

mod14

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
allfiles/AZ-301T02/Module_02/LabFiles/Starter
allfiles/AZ-301T02/Module_02/LabFiles/Starter
 
 
README.md
README.md
 
 

README.md

Comparing Database Options in Azure

Lab: Deploying NoSQL Database Instances in Azure

Exercise 1: Deploy a Cosmos DB database

Task 1: Open the Azure Portal

  1. On the Taskbar, click the Microsoft Edge icon.

  2. In the open browser window, navigate to the Azure Portal (https://portal.azure.com).

  3. If prompted, authenticate with the user account account that has the owner role in the Azure subscription you will be using in this lab.

Task 2: Create a Cosmos DB database and collection

  1. In the upper left corner of the Azure portal, click Create a resource.

  2. At the top of the New blade, in the Search the Marketplace text box, type Cosmos DB and press Enter.

  3. On the Everything blade, in the search results, click Azure Cosmos DB.

  4. On the Azure Cosmos DB blade, click the Create button.

  5. On the new Azure Cosmos DB blade, perform the following tasks:

    • Leave the Subscription drop-down list entry set to its default value.

    • Resource group: ensure that the Create new option is selected and then, in the text box, type AADesignLab0701-RG.

    • In the Account Name text box, type cosmosdb(YourName).

    • In the API drop-down list, select the Core (SQL) option.

    • In the Location drop-down list, select (Asia Pacific) Southeast Asia.

    • Leave all remaining settings with their default values.

    • Click the Review + create button and then click the Create button.

  6. Wait for the provisioning to complete before you proceed to the next step.

    Note: The deployment could take up to 10 to 15 minutes.

  7. Navigate to the blade of the newly created Cosmos DB account and click Keys.

  8. On the Cosmos DB account Keys blade, note the value of the PRIMARY CONNECTION STRING. You will need it in the third exercise of this lab.

    Note: Example primary connection string: AccountEndpoint=https://cosmosdbstv.documents.azure.com:443/;AccountKey=n98TNtaQJsSKHqJT6sUcGQ5RJ8seYzLlrDPqxhMxafz2SoC24ETyvFQiHyA7R7vdGGGLPW7nxziHpLAEfvzTQA==;

  9. At the top of the portal, click the Cloud Shell icon to open a new shell instance.

    Note: The Cloud Shell icon is a symbol that is constructed of the combination of the greater than and underscore characters.

  10. If this is your first time opening the Cloud Shell using your subscription, you will see a wizard to configure Cloud Shell for first-time usage. When prompted, in the Welcome to Azure Cloud Shell pane, click Bash (Linux).

    Note: If you do not see the configuration options for Cloud Shell, this is most likely because you are using an existing subscription with this course's labs.

  11. Wait for the Cloud Shell to finish its setup procedures before you proceed to the next task.

  12. At the Cloud Shell command prompt, type in the following command and press Enter to create a variable which value designates the name of the resource group that contains the Azure Cosmos DB account you deployed earlier in this task:

    RESOURCE_GROUP='AADesignLab0701-RG'

  13. At the Cloud Shell command prompt, type in the following command and press Enter to create a variable which value designates the name of the CosmosDB account you created earlier in this task:

    COSMOSDB_NAME=$(az cosmosdb list --resource-group $RESOURCE_GROUP --query "[0].name" --output tsv)

  14. At the Cloud Shell command prompt, type in the following command and press Enter to create a variable which value designates the primary key of the CosmosDB account you created earlier in this task:

    PRIMARY_KEY=$(az cosmosdb keys list --resource-group $RESOURCE_GROUP --name $COSMOSDB_NAME --output json | jq -r '.primaryMasterKey')

  15. At the Cloud Shell command prompt, type in the following command and press Enter to create a variable which value designates the URI of the CosmosDB account you created earlier in this task:

    URI="https://$COSMOSDB_NAME.documents.azure.com:443/"

  16. At the Cloud Shell command prompt, type in the following command and press Enter to create a new CosmosDB database named FinancialClubDatabase:

    az cosmosdb database create --url-connection $URI --key $PRIMARY_KEY --db-name 'FinancialClubDatabase'

  17. At the Cloud Shell command prompt, type in the following command and press Enter to create a fixed collection named MemberCollection in the newly created database:

    az cosmosdb collection create --url-connection $URI --key $PRIMARY_KEY --db-name 'FinancialClubDatabase' --collection-name 'MemberCollection' --throughput 400

  18. At the Cloud Shell command prompt, type in the following command and press Enter to display the value of the PRIMARY_KEY variable:

    echo $PRIMARY_KEY

  19. At the Cloud Shell command prompt, type in the following command and press Enter to display the value of the URI variable:

    echo $URI

    Note: Take a note of these values - you will need them in the third exercise of this lab.

Task 3: Create and query documents in Cosmos DB

  1. On the left side of the Azure Cosmos DB account blade, click Data Explorer.

  2. In the Data Explorer pane, if necessary, refresh the pane and then click the MemberCollection child node of the FinancialClubDatabase node.

  3. Click the New SQL Query button at the top of the Data Explorer pane.

  4. In the Query 1 tab that opened, view the default query:

    SELECT * FROM c

  5. Click the Execute Query button at the top of the query editor and verify that the query does not return any results.

  6. In the left pane of the Data Explorer, expand the MemberCollection node.

  7. Click the Items child node within the MemberCollection node.

  8. In the new Items tab that opened, click the New Item button at the top of the tab.

  9. In the Items tab, replace the existing document with the following document:

    {
    "firstName": "Pennington",
    "lastName": "Oneal",
    "age": 26,
    "salary": 90000.00,
    "company": "Veraq",
    "isVested": false
}

  10. Click the Save button at the top of the Items tab (you might need to first click the ellipsis toolbar button).

  11. In the Items tab, click the New Item button at the top of the tab.

  12. In the Items tab, replace the existing document with the following document:

    {
    "firstName": "Suzanne",
    "lastName": "Oneal",
    "company": "Veraq"
}

  13. Click the Save button at the top of the Items tab.

  14. Switch back to the Query 1 tab, re-run the default query SELECT * FROM c by clicking the Execute Query button at the top of the query editor, and review the results.

  15. In the query editor, replace the default query with the following query:

    SELECT
    c.id,
    c.firstName,
    c.lastName,
    c.isVested,
    c.company
FROM
    c
WHERE
    IS_DEFINED(c.isVested)

  16. Click the Execute Query button at the top of the query editor and review the results.

  17. In the query editor, replace the existing query with the following query:

    SELECT
    c.id,
    c.firstName,
    c.lastName,
    c.age
FROM
    c
WHERE
    c.age > 20

  18. Click the Execute Query button at the top of the query editor and review the results.

  19. In the query editor, replace the existing query with the following query:

    SELECT VALUE
    c.id
FROM
    c

  20. Click the Execute Query button at the top of the query editor and review the results.

  21. In the query editor, replace the existing query with the following query:

    SELECT VALUE {
    "badgeNumber": SUBSTRING(c.id, 0, 8),
    "company": c.company,
    "fullName": CONCAT(c.firstName, " ", c.lastName)
} FROM c

  22. Click the Execute Query button at the top of the query editor and review the results.

Review: In this exercise, you created a new Cosmos DB account, database, and collection, added sample items to the collection, and run sample queries targeting these items.

Exercise 2: Deploy Application using Cosmos DB

Task 1: Deploy API App code using Azure Resource Manager templates and GitHub

  1. In the upper left corner of the Azure portal, click Create a resource.

  2. At the top of the New blade, in the Search the Marketplace text box, type Template Deployment and press Enter.

  3. On the Everything blade, in the search results, click Template Deployment.

  4. On the Template deployment blade, click the Create button.

  5. On the Custom deployment blade, click the Build your own template in the editor link.

  6. On the Edit template blade, click the Load file link.

  7. In the Open file dialog that appears, navigate to the \allfiles\AZ-301T02\Module_02\LabFiles\Starter\ folder.

  8. Select the api.json file.

  9. Click the Open button.

  10. Back on the Edit template blade, click the Save button to persist the template.

  11. Back on the Custom deployment blade, perform the following tasks:

    • Leave the Subscription drop-down list entry set to its default value.

    • In the Resource group section, select the Use existing option and then, in the drop-down list, select AADesignLab0701-RG.

    • Click the Create button.

  12. Wait for the deployment to complete before you proceed to the next task.

    Note: Deployment from source control can take up to 10 minutes.

Task 2: Validate API App

  1. In the hub menu in the Azure portal, click Resource groups.

  2. On the Resource groups blade, click AADesignLab0701-RG.

  3. On the AADesignLab0701-RG blade, click the entry representing the newly created App Service API app.

  4. On the API app blade, under Settings, click Configuration.

  5. On the Application Settings blade, scroll down to the Application settings section and perform the following tasks:

    • Set the value of the CosmosDB:AuthorizationKey setting to the value of the PRIMARY KEY setting of the Cosmos DB account you created earlier in this lab.

    • Update the value of the CosmosDB:EndpointUrl setting to the value of the URI setting of the Cosmos DB instance you created earlier in this lab.

    • Click the Save button at the top of the pane (if prompted, click Continue).

  6. On the left-side of the API app blade, click Overview.

  7. Click the Restart button at the top of the blade and, when prompted to confirm, click Yes.

  8. Click the Browse button at the top of the blade. This will open a new browser tab displaying the Swagger UI homepage.

    Note: If you click the Browse button before the API app has fully restarted, you may not be able to follow the remaining steps in this task. If this happens, refresh your browser until the API app is running again.

  9. On the Swagger UI homepage, click GET/Documents.

  10. Click the Try it out! button.

  11. Review the results of the request (the results should include 2 items).

  12. Back on the Swagger UI homepage, click POST/Populate.

  13. In the Parameters section, in the Value field for the options parameter, paste in the following JSON content:

    {
    "quantity": 50
}

  14. In the Response Messages section, click the Try it out! button.

  15. Review the results of the request (the results should include 50 items).

  16. Back on the Swagger UI homepage, click GET/Documents.

  17. Locate the Response Messages section. Click the Try it out! button.

  18. Review the results of the request (the results should include 52 items).

  19. Close the new browser tab and return to the browser tab displaying the Azure portal.

Review: In this exercise, you created a new API App that uses the .NET Core DocumentDB SDK to connect to Azure Cosmos DB collection and manage its documents.

Exercise 3: Connect Cosmos DB to Azure Search

Task 1: Create Azure Cognitive Search Instance

  1. In the upper left corner of the Azure portal, click Create a resource.

  2. At the top of the New blade, in the Search the Marketplace text box, type Search and press Enter.

  3. On the Showing All Results blade, in the search results, click Azure Cognitive Search.

  4. On the Azure Cognitive Search blade, click the Create button.

  5. On the New Search Service blade, perform the following tasks:

    • Leave the Subscription drop-down list entry set to its default value.

    • In the Resource group section, select the Use existing option and then, in the drop-down list, select AADesignLab0701-RG.

    • In the URL text box, enter a globally unique name. Record its value. You will use it later in this lab.

    • In the Location drop-down list, select the Azure region matching or near the location where you deployed Cosmos DB resource earlier in this labb

    • Click Change Pricing Tier.

    • On the Select Pricing Tier blade, click Free and then click the Select button.

    • Click the Review + create button, review the settings then click Create.

  6. Wait for the provisioning to complete before you proceed to the next step.

  7. In the hub menu in the Azure portal, click Resource groups.

  8. On the Resource groups blade, click AADesignLab0701-RG.

  9. On the AADesignLab0701-RG blade, click the entry representing the newly created Azure Search instance.

  10. On the Search service blade, click Keys.

  11. In the Keys pane, record the value of QUERY KEY. You will use it later in this lab.

    Note: The query key is located below the primary and secondary keys, and does not have a name by default.

Task 2: Index Cosmos DB Data in Azure Search

  1. In the hub menu in the Azure portal, click Resource groups.

  2. On the Resource groups blade, click AADesignLab0701-RG.

  3. On the AADesignLab0701-RG blade, click the entry representing the Azure Search instance you created earlier in this lab.

  4. On the Overview blade of Azure Search service, click Import data.

  5. On the Connect to your data tab, perform the following tasks:

    • In the Data Source drop down list, select Cosmos DB.

    • In the Name text box, type cosmosdata.

    • In the Cosmos DB account text box, type the Cosmos DB account connection string you identfied earlier in this lab.

    • In the Database drop-down list, select the FinancialClubDatabase entry.

    • in the Collection drop-down list, select the MemberCollection entry.

    • In the Query field, enter the following SQL query:

      SELECT
    c.id,
    c.firstName,
    c.lastName,
    c.age,
    c.salary,
    c.company,
    c.isVested,
    c._ts
FROM
    c
WHERE
    c._ts >= @HighWaterMark
ORDER BY c._ts

    • Ensure that the Query results ordered by _ts checkbox is selected.

    • Click the Next: Add cognitive skills (optional) button.

  6. On the Cognitive Search blade, click the Skip to: Customize target index button.

  7. On the Customize target index blade, perform the following tasks:

    • In the Index name text box, type memberindex.

    • In the Key drop-down list, ensure that the id entry is selected.

    • For the id field in the table, ensure that the RETRIEVABLE, FILTERABLE, and SORTABLE checkboxes are selected.

    • For the firstName field in the table, ensure that the RETRIEVABLE, SORTABLE, and SEARCHABLE options are selected.

    • For the lastName field in the table, ensure that the RETRIEVABLE, SORTABLE, and SEARCHABLE checkboxes are selected.

    • For the age field in the table, ensure that the RETRIEVABLE, FILTERABLE, SORTABLE, and FACETABLE checkboxes are selected.

    • For the salary field in the table, ensure that the RETRIEVABLE, FILTERABLE, SORTABLE, and FACETABLE checkboxes are selected.

    • For the company field in the table, ensure that the RETRIEVABLE, FACETABLE, and SEARCHABLE checkboxes are selected.

    • For the isVested field in the table, ensure that the RETRIEVABLE, FILTERABLE, SORTABLE, FACETABLE checkboxes are selected.

    • Click the Next: Create an indexer button.

  8. On the Create an Indexer blade, perform the following tasks:

    • In the Name text box, type cosmosmemberindexer.

    • In the Schedule section, select the Custom option.

    • In the Interval (minutes) text box, type 5.

    • In the Start time (UTC) field, specify the current date and accept the default value of the time entry.

    • Ensure that the Track deletions checkbox is clear and click the Submit button.

Task 3: Validate API App

  1. In the hub menu in the Azure portal, click Resource groups.

  2. On the Resource groups blade, click AADesignLab0701-RG.

  3. On the AADesignLab0701-RG blade, click the entry representing the App Service API app you created earlier in this lab.

  4. On the API app blade, click Configuration.

  5. On the Application settings blade, scroll down to the Application settings section and perform the following tasks:

    • Set the value of the Search:AccountName setting to the name of the Azure Search instance you created earlier in this lab.

    • Set the value of the Search:QueryKey setting to the value of the QUERY KEY of the Azure Search instance you created earlier in this lab.

    • Set the value of the Search:IndexId setting to the value memberindex.

    • Click the Save button at the top of the blade (if prompted, click Continue).

  6. On the API app blade, click Overview.

  7. Click the Restart button at the top of the blade and, when prompted to confirm, click Yes.

  8. Click the Browse button at the top of the blade. This will open a new browser tab displaying the Swagger UI homepage.

    Note: If you click the Browse button before the API app has fully restarted, you may not be able to follow the remaining steps in this task. If this happens, refresh your browser until the API app is running again.

  9. On the Swagger UI homepage, click Cosmos DB API v.1.0.0 at the top of the page and select the Cosmos DB API v.2.0.0 option from the drop-down list.

  10. Click GET/Documents/search.

  11. In the Parameters section, in the Value text box of the query parameter, type the following text:

    Oneal

  12. In the Response Messages section, click the Try it out! button.

  13. Review the results of the request (the results should include 2 items).

  14. In the Parameters section, in the Value text box of the query parameter, type the following text:

    penn*

  15. In the Response Messages section, click the Try it out! button.

  16. Review the results of the request (the results should include 1 item).

  17. Close the new browser tab and return to the browser tab displaying the Azure portal.

Review: In this exercise, you created an Azure Search instance that uses an indexer to index the documents in Azure Cosmos DB.

Exercise 4: Remove lab resources

Task 1: Delete the resource group

  1. At the Cloud Shell command prompt, type in the following command and press Enter to delete the resource groups you created in this lab

    az group list --query "[?starts_with(name,'AADesignLab0701')]".name --output tsv | xargs -L1 bash -c 'az group delete --name $0 --no-wait --yes'

Review: In this exercise, you removed the resources used in this lab.