Skip to content

Commit bfe8a61

Browse files
MScalopezMScalopez
committed
Updated connection instructions to make them clearer
1 parent 2704a12 commit bfe8a61

5 files changed

Lines changed: 58 additions & 8 deletions

‎Instructions/Labs/06-optimize-database-performance.md‎

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,11 @@ First, create an Azure SQL Database with sample data.
4747
| **Subscription** | Select your Azure subscription. |
4848
| **Resource group** | Select or create a resource group. |
4949
| **Database name** | *AdventureWorksLT* |
50-
| **Server** | Select **Create new** and create a new server with a unique name. Select your **Location**. You should use **Use Microsoft Entra-only authentication** for more secure access, or **Use both SQL and Microsoft Entra authentication**/**SQL authentication** with an admin sign in and password, but note that *Microsoft Entra-only authentication* is recommended. Select **OK**. |
50+
| **Server** | Select **Create new** and create a new server with a unique name. Select your **Location**. For authentication, select one of the following options and then select **OK**: |
51+
52+
> 📝 **Authentication is not optional** — you must choose the method that matches your organization's security policies. Each option affects how you connect to the database later:
53+
> - **Use Microsoft Entra-only authentication** *(recommended)*: Select this if your organization requires Entra-based access. Set your Azure account as the **Microsoft Entra admin**. You connect to the database using your Microsoft Entra account (for example, in SSMS select *Authentication* = **Microsoft Entra MFA**).
54+
> - **Use both SQL and Microsoft Entra authentication/SQL authentication**: Select this if you prefer a SQL admin login or your organization allows both methods. Provide a **Server admin login** and **Password** — you need these credentials to connect. You can also set a **Microsoft Entra admin** to enable Entra logins alongside SQL auth.
5155
5256
> 📝 If you already have a test server you can use, select it instead of creating a new one.
5357
@@ -73,6 +77,12 @@ First, create an Azure SQL Database with sample data.
7377
The AdventureWorksLT sample database has product and customer data, but its tables are small. You need a larger table to produce meaningful execution plans and query statistics. In this section, you create an `OrderHistory` table with 80,000 rows that simulates a year of order data.
7478

7579
1. Connect to your Azure SQL Database using SSMS.
80+
81+
> 💡 **How to connect** depends on which authentication method your organization supports and was configured during server creation:
82+
> - **Microsoft Entra authentication**: Set *Authentication* to **Microsoft Entra MFA** and sign in with your Azure account.
83+
> - **SQL authentication**: Enter the **Server admin login** and **Password** you specified during server creation, with *Authentication* set to **SQL Login**.
84+
>
85+
> In both cases, set the **Server name** to `<your-server-name>.database.windows.net` and the **Database** to **AdventureWorksLT**.
7686
1. Run the following script to create and populate the `OrderHistory` table:
7787

7888
```sql

‎Instructions/Labs/07-implement-cicd-sql-database-projects.md‎

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,11 @@ First, create an Azure SQL Database with sample data.
5151
| **Subscription** | Select your Azure subscription. |
5252
| **Resource group** | Select or create a resource group. |
5353
| **Database name** | *AdventureWorksLT* |
54-
| **Server** | Select **Create new** and create a new server with a unique name. Select your **Location**. You should use **Use Microsoft Entra-only authentication** for more secure access, or **Use both SQL and Microsoft Entra authentication**/**SQL authentication** with an admin sign in and password, but note that *Microsoft Entra-only authentication* is recommended. Select **OK**. |
54+
| **Server** | Select **Create new** and create a new server with a unique name. Select your **Location**. For authentication, select one of the following options and then select **OK**: |
55+
56+
> &#128221; **Authentication is not optional** — you must choose the method that matches your organization's security policies. Each option affects how you connect to the database later:
57+
> - **Use Microsoft Entra-only authentication** *(recommended)*: Select this if your organization requires Entra-based access. Set your Azure account as the **Microsoft Entra admin**. You connect to the database using your Microsoft Entra account (for example, in SSMS select *Authentication* = **Microsoft Entra MFA**).
58+
> - **Use both SQL and Microsoft Entra authentication/SQL authentication**: Select this if you prefer a SQL admin login or your organization allows both methods. Provide a **Server admin login** and **Password** — you need these credentials to connect. You can also set a **Microsoft Entra admin** to enable Entra logins alongside SQL auth.
5559
5660
> &#128221; If you already have a test server you can use, select it instead of creating a new one.
5761

‎Instructions/Labs/09-generate-update-embedings-sql.md‎

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,13 @@ First, create an Azure SQL Database with sample data.
4747
| **Subscription** | Select your Azure subscription. |
4848
| **Resource group** | Select or create a resource group. |
4949
| **Database name** | *AdventureWorksLT* |
50-
| **Server** | Select **Create new** and create a new server with a unique name. Select your **Location**. You should use **Use Microsoft Entra-only authentication** for more secure access, or **Use both SQL and Microsoft Entra authentication**/**SQL authentication** with an admin sign in and password, but note that *Microsoft Entra-only authentication* is recommended. Select **OK**. |
50+
| **Server** | Select **Create new** and create a new server with a unique name. Select your **Location**. For authentication, select one of the following options and then select **OK**: |
51+
52+
> &#128221; **Authentication is not optional** — you must choose the method that matches your organization's security policies. Each option affects how you connect to the database later:
53+
> - **Use Microsoft Entra-only authentication** *(recommended)*: Select this if your organization requires Entra-based access. Set your Azure account as the **Microsoft Entra admin**. You connect to the database using your Microsoft Entra account (for example, in SSMS select *Authentication* = **Microsoft Entra MFA**).
54+
> - **Use both SQL and Microsoft Entra authentication/SQL authentication**: Select this if you prefer a SQL admin login or your organization allows both methods. Provide a **Server admin login** and **Password** — you need these credentials to connect. You can also set a **Microsoft Entra admin** to enable Entra logins alongside SQL auth.
55+
>
56+
> The authentication method you choose here controls how *you* connect to the database as a developer. It is separate from how Azure SQL connects to Azure OpenAI, which is configured later in the lab.
5157
5258
> &#128221; If you already have a test server you can use, select it instead of creating a new one.
5359
@@ -132,7 +138,13 @@ Since Azure SQL Database uses a system-assigned managed identity to authenticate
132138

133139
The AdventureWorksLT sample database contains product information but no customer reviews. In this step, you download and run a script that creates a **ProductReview** table with 140 realistic reviews across many product categories. These reviews provide the text data that you generate embeddings for in this exercise.
134140

135-
1. Connect to your Azure SQL Database using Visual Studio Code or SQL Server Management Studio.
141+
1. Connect to your Azure SQL Database using Visual Studio Code (with the SQL Server extension) or SQL Server Management Studio.
142+
143+
> &#128161; **How to connect** depends on which authentication method your organization supports and was configured during server creation:
144+
> - **Microsoft Entra authentication**: In SSMS, set *Authentication* to **Microsoft Entra MFA** and sign in with your Azure account. In VS Code, select the **Microsoft Entra ID** authentication type when creating a connection profile.
145+
> - **SQL authentication**: In SSMS or VS Code, enter the **Server admin login** and **Password** you specified during server creation, with *Authentication* set to **SQL Login**.
146+
>
147+
> In both cases, set the **Server name** to `<your-server-name>.database.windows.net` and the **Database** to **AdventureWorksLT**.
136148
1. Download the review script from [**product-reviews-insert.sql**](https://raw.githubusercontent.com/MicrosoftLearning/mslearn-sql-developer/main/Allfiles/product-reviews-insert.sql) and save it locally.
137149
1. Open the downloaded file and run the entire script against your **AdventureWorksLT** database.
138150
1. Verify the table was created and populated by running:

‎Instructions/Labs/10-implement-intelligent-search.md‎

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,13 @@ First, create an Azure SQL Database with sample data.
4848
| **Subscription** | Select your Azure subscription. |
4949
| **Resource group** | Select or create a resource group. |
5050
| **Database name** | *AdventureWorksLT* |
51-
| **Server** | Select **Create new** and create a new server with a unique name. Select your **Location**. You should use **Use Microsoft Entra-only authentication** for more secure access, or **Use both SQL and Microsoft Entra authentication**/**SQL authentication** with an admin sign in and password, but note that *Microsoft Entra-only authentication* is recommended. Select **OK**. |
51+
| **Server** | Select **Create new** and create a new server with a unique name. Select your **Location**. For authentication, select one of the following options and then select **OK**: |
52+
53+
> &#128221; **Authentication is not optional** — you must choose the method that matches your organization's security policies. Each option affects how you connect to the database later:
54+
> - **Use Microsoft Entra-only authentication** *(recommended)*: Select this if your organization requires Entra-based access. Set your Azure account as the **Microsoft Entra admin**. You connect to the database using your Microsoft Entra account (for example, in SSMS select *Authentication* = **Microsoft Entra MFA**).
55+
> - **Use both SQL and Microsoft Entra authentication/SQL authentication**: Select this if you prefer a SQL admin login or your organization allows both methods. Provide a **Server admin login** and **Password** — you need these credentials to connect. You can also set a **Microsoft Entra admin** to enable Entra logins alongside SQL auth.
56+
>
57+
> The authentication method you choose here controls how *you* connect to the database as a developer. It is separate from how Azure SQL connects to Azure OpenAI, which is configured later in the lab.
5258
5359
> &#128221; If you already have a test server you can use, select it instead of creating a new one.
5460
@@ -133,7 +139,13 @@ Since Azure SQL Database uses a system-assigned managed identity to authenticate
133139

134140
The AdventureWorksLT sample database contains product information but no customer reviews. In this step, you download and run a script that creates a **ProductReview** table with 140 realistic reviews across many product categories. These reviews provide rich text data to search through using full-text, vector, and hybrid search.
135141

136-
1. Connect to your Azure SQL Database using Visual Studio Code or SQL Server Management Studio.
142+
1. Connect to your Azure SQL Database using Visual Studio Code (with the SQL Server extension) or SQL Server Management Studio.
143+
144+
> &#128161; **How to connect** depends on which authentication method your organization supports and was configured during server creation:
145+
> - **Microsoft Entra authentication**: In SSMS, set *Authentication* to **Microsoft Entra MFA** and sign in with your Azure account. In VS Code, select the **Microsoft Entra ID** authentication type when creating a connection profile.
146+
> - **SQL authentication**: In SSMS or VS Code, enter the **Server admin login** and **Password** you specified during server creation, with *Authentication* set to **SQL Login**.
147+
>
148+
> In both cases, set the **Server name** to `<your-server-name>.database.windows.net` and the **Database** to **AdventureWorksLT**.
137149
1. Download the review script from [**product-reviews-insert.sql**](https://raw.githubusercontent.com/MicrosoftLearning/mslearn-sql-developer/main/Allfiles/product-reviews-insert.sql) and save it locally.
138150
1. Open the downloaded file and run the entire script against your **AdventureWorksLT** database.
139151
1. Verify the table was created and populated by running:

‎Instructions/Labs/11-implement-rag-solutions.md‎

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,13 @@ First, create an Azure SQL Database with sample data.
4848
| **Subscription** | Select your Azure subscription. |
4949
| **Resource group** | Select or create a resource group. |
5050
| **Database name** | *AdventureWorksLT* |
51-
| **Server** | Select **Create new** and create a new server with a unique name. Select your **Location**. You should use **Use Microsoft Entra-only authentication** for more secure access, or **Use both SQL and Microsoft Entra authentication**/**SQL authentication** with an admin sign in and password, but note that *Microsoft Entra-only authentication* is recommended. Select **OK**. |
51+
| **Server** | Select **Create new** and create a new server with a unique name. Select your **Location**. For authentication, select one of the following options and then select **OK**: |
52+
53+
> &#128221; **Authentication is not optional** — you must choose the method that matches your organization's security policies. Each option affects how you connect to the database later:
54+
> - **Use Microsoft Entra-only authentication** *(recommended)*: Select this if your organization requires Entra-based access. Set your Azure account as the **Microsoft Entra admin**. You connect to the database using your Microsoft Entra account (for example, in SSMS select *Authentication* = **Microsoft Entra MFA**).
55+
> - **Use both SQL and Microsoft Entra authentication/SQL authentication**: Select this if you prefer a SQL admin login or your organization allows both methods. Provide a **Server admin login** and **Password** — you need these credentials to connect. You can also set a **Microsoft Entra admin** to enable Entra logins alongside SQL auth.
56+
>
57+
> The authentication method you choose here controls how *you* connect to the database as a developer. It is separate from how Azure SQL connects to Azure OpenAI, which is configured later in the lab.
5258
5359
> &#128221; If you already have a test server you can use, select it instead of creating a new one.
5460
@@ -133,7 +139,13 @@ Since Azure SQL Database uses a system-assigned managed identity to authenticate
133139

134140
The AdventureWorksLT sample database contains product information but no customer reviews. In this step, you download and run a script that creates a **ProductReview** table with 140 realistic reviews across many product categories. These reviews give the RAG solution rich, varied content to search through.
135141

136-
1. Connect to your Azure SQL Database using Visual Studio Code or SQL Server Management Studio.
142+
1. Connect to your Azure SQL Database using Visual Studio Code (with the SQL Server extension) or SQL Server Management Studio.
143+
144+
> &#128161; **How to connect** depends on which authentication method your organization supports and was configured during server creation:
145+
> - **Microsoft Entra authentication**: In SSMS, set *Authentication* to **Microsoft Entra MFA** and sign in with your Azure account. In VS Code, select the **Microsoft Entra ID** authentication type when creating a connection profile.
146+
> - **SQL authentication**: In SSMS or VS Code, enter the **Server admin login** and **Password** you specified during server creation, with *Authentication* set to **SQL Login**.
147+
>
148+
> In both cases, set the **Server name** to `<your-server-name>.database.windows.net` and the **Database** to **AdventureWorksLT**.
137149
1. Download the review script from [**product-reviews-insert.sql**](https://raw.githubusercontent.com/MicrosoftLearning/mslearn-sql-developer/main/Allfiles/product-reviews-insert.sql) and save it locally.
138150
1. Open the downloaded file and run the entire script against your **AdventureWorksLT** database.
139151
1. Verify the table was created and populated by running:

0 commit comments

Comments
 (0)