Merge pull request #54139 from staleycyn/patch-3

Content drift changes for the design relational db module

Author: JamesJBarnett

learn-pr/wwl-azure/design-data-storage-solution-for-relational-data/includes/1-introduction.md

@@ -6,7 +6,7 @@ Many organizations have an aging or under-engineered data platform strategy. The
 
 Tailwind Traders is a fictitious home improvement retailer. The company operates retail hardware stores across the globe and online. It currently manages an on-premises datacenter that hosts the company's retail website. The datacenter also stores all of the data and streaming video for its applications. The on-premises SQL Server provides storage for customer data, order history, and product catalogs. SQL Server also serves as data storage for the internal-only training portal website. The company wants to effectively manage their database needs by migrating their infrastructure to the cloud. 
 
-As you work through this lesson, suppose you're the CTO for Tailwind Traders. You're tasked with finding a cost efficient database solution that provides low latency and high availability. In this module, you explore different storage solutions that solve different types of problems. You review storage options offered by Azure SQL Database, Azure SQL Managed Instance, and SQL Server in an Azure virtual machine. You discover how to work with data in Azure SQL Edge and Azure Cosmos DB. You also learn how to design your solution with data protection. 
+As you work through this lesson, suppose you're the CTO for Tailwind Traders. You're tasked with finding a cost efficient database solution that provides low latency and high availability. In this module, you explore different storage solutions that solve different types of problems. You review storage options offered by Azure SQL Database, Azure SQL Managed Instance, and SQL Server in an Azure virtual machine. You discover how to work with data in Azure Cosmos DB. You also learn how to design your solution with data protection. 
 
 ### Learning objectives
 
@@ -24,23 +24,11 @@ In this module, you learn how to:
 
 - Design protection for data at rest, data in transmission, and data in use.
 
-- Design for Azure Cosmos DB and Cosmos DB Table API. 
+- Design for Azure Cosmos DB and Azure Cosmos DB for Table. 
 
 ### Skills measured
 
-The content in this module helps you prepare for [Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions](/credentials/certifications/exams/az-305/). The module concepts are covered in:
-
-Design data storage solutions
-
-- Design a data storage solution for relational data
-
-   - Recommend a solution for storing relational data.
-
-   - Recommend a database service tier and compute tier.
-
-   - Recommend a solution for database scalability.
-
-   - Recommend a solution for data protection.
+The content in this module helps you prepare for [Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions](/credentials/certifications/exams/az-305/). 
 
 ### Prerequisites
 

learn-pr/wwl-azure/design-data-storage-solution-for-relational-data/includes/10-summary-resources.md

@@ -1,4 +1,4 @@
-In this module, you learned how to design a cost efficient database solution that provides low latency, high availability, and scalability. You examined options for moving relational data workloads to the cloud. You explored scenarios for using Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure Virtual Machines. You reviewed how to work with data in Azure SQL Edge, Azure Cosmos DB, and Azure Table Storage. You discovered how to protect data at rest, data in transmission, and data in use by using different security and encryption methods. 
+In this module, you learned how to design a cost efficient database solution that provides low latency, high availability, and scalability. You examined options for moving relational data workloads to the cloud. You explored scenarios for using Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure Virtual Machines. You reviewed how to work with data in Azure Cosmos DB, and Azure Table Storage. You discovered how to protect data at rest, data in transmission, and data in use by using different security and encryption methods. 
 
 ## Learn more with Copilot
 
@@ -14,28 +14,19 @@ Copilot can assist you in designing Azure infrastructure solutions. Copilot can
 
 ## Learn more with Azure documentation
 
-- Explore [SQL Server on Azure Virtual Machines](https://azure.microsoft.com/services/virtual-machines/sql-server/).
+- Explore [SQL Server on Azure Virtual Machines](/azure/azure-sql/virtual-machines/).
 
-- Explore [Azure SQL Managed Instance](https://azure.microsoft.com/products/azure-sql/managed-instance/).
+- Explore [Azure SQL Managed Instance](/azure/azure-sql/managed-instance/).
 
-- Explore [Azure SQL Database](https://azure.microsoft.com/products/azure-sql/database/).
+- Explore [Azure SQL Database](/azure/azure-sql/database/).
 
-- Read about [Azure Cosmos DB](/azure/cosmos-db/introduction).
+- Explore [Azure Cosmos DB](/azure/cosmos-db/overview/).
 
-- Review [FAQ about the Table API in Azure Cosmos DB](/azure/cosmos-db/table/table-api-faq).
-
-- Discover [Azure SQL Database serverless](/azure/azure-sql/database/serverless-tier-overview).
-
-- Build [scalable cloud databases](/azure/azure-sql/database/elastic-database-client-library).
-
-- Scale out with [Azure SQL Database](/azure/azure-sql/database/elastic-scale-introduction).
-
-- Use [elastic pools to manage and scale multiple databases in Azure SQL Database](/azure/azure-sql/database/elastic-pool-overview).
 
 ## Learn more with self-paced training
 
-- Work with [Azure Cosmos DB](/training/modules/work-with-cosmos-db/).
+- Learn more with [Introduction to Azure Cosmos DB for NoSQL](/training/modules/introduction-to-azure-cosmos-db-sql-api/).
 
-- Explore [Azure database and analytics services](/training/modules/azure-database-fundamentals/).
+- Learn more with [Plan and implement security for Azure SQL Database and Azure SQL Managed Instance](/training/modules/security-azure-sql-database-azure-sql-managed-instance/).
 
-- Explore [relational database services in Azure](/training/modules/explore-provision-deploy-relational-database-offerings-azure/).
+- Learn more with [Get started with SQL Server 2025](/training/modules/introduction-to-sql-server/).

learn-pr/wwl-azure/design-data-storage-solution-for-relational-data/includes/2-design-for-azure-sql-database.md

@@ -17,7 +17,7 @@ Review the following characteristics of the SQL Database deployment option:
 
 - It's a highly scalable, intelligent, relational database service built for the cloud with the industry's highest availability.
 
-- SQL Database is the only deployment option that supports scenarios that require large databases (currently up to 100 TB) or autoscaling for unpredictable workloads (serverless).
+- SQL Database is the only deployment option that supports scenarios that require large databases (currently up to 128 TB) or autoscaling for unpredictable workloads (serverless).
 
 - You can create a **SQL Database elastic database pool**, where all databases in the pool share the same set of compute and storage resources. Each database can use the resources it needs, within the limits you set, depending on current load.
 
@@ -29,7 +29,7 @@ Review the following characteristics of the SQL Database deployment option:
 
    - **DTU**: A DTU (Database Transaction Unit) is a combined measure of compute, storage, and I/O resources. The DTU option is an easy, preconfigured purchase option.
 
-   - **Serverless**: A compute tier for single databases in SQL Database. The serverless model automatically scales compute, based on workload demand, and bills only for the amount of compute used. 
+   - **Serverless**: Available for General Purpose and Hyperscale databases, serverless automatically scales compute and charges for what you use. Hyperscale serverless also supports large storage.
 
 #### Business scenario
 
@@ -41,6 +41,8 @@ Let's explore a business scenario for Azure SQL Database. AccuWeather has been a
 
 Consider how Azure SQL Database can be included in your relational data storage plan for Tailwind Traders:
 
+- **Consider the free offer for development and testing**: Azure SQL Database provides a free offer for the lifetime of your subscription—up to 10 General Purpose single databases, each with 100,000 vCore seconds of compute per month. The free offer is useful for prototyping, development, and nonproduction environments.
+
 - **Consider vCore pricing**. (Microsoft recommended) Select compute and storage resources independently for multiple SQL databases or an elastic database pool. Use Azure Hybrid Benefit for SQL Server or reserved capacity (pay in advance) to save money. You control the compute and storage resources that you create and pay for. 
 
 - **Consider DTU pricing**. Choose this easy, preconfigured purchase plan for a bundled measure of compute, storage, and I/O resources to support multiple SQL databases. This option isn't available for Azure SQL Managed Instance.

learn-pr/wwl-azure/design-data-storage-solution-for-relational-data/includes/3-design-for-azure-sql-managed-instance.md

@@ -24,6 +24,11 @@ Let's explore a business scenario for Azure SQL Managed Instance. Komatsu is a m
 
 Consider how Azure SQL Managed Instance can be included in your relational data storage plan for Tailwind Traders:
 
+- **Consider the free offer for evaluation**: Azure SQL Managed Instance offers a free instance for 12 months after creation. The free offer allows teams to evaluate lift-and-shift migrations. You can test CLR and Service Broker workloads. It's possible to validate compatibility. There's no initial cost commitment.
+
 - **Consider instance-scoped features**. Use instance-scoped features of Azure SQL Managed Instance like Service Broker, CLR, SQL Server Agent, and Linked servers. Migrate your relational and structured data to Azure without rearchitecting your applications. 
 
-- **Consider instance scalability**. Add scalability for your instance by enabling vCores mode. You can define the maximum CPU cores and storage for your instances, so all databases in the instance share the same resources.
+- **Consider instance scalability**. Add scalability for your instance by enabling vCores mode. You can define the maximum CPU cores and storage for your instances, so all databases in the instance share the same resources.
+
+- **Consider upgrading to Next-gen General Purpose for more capacity**: This tier supports up to 500 databases per instance, 32 TB of storage, and lets you scale resources independently. This capacity is provided at the same cost as General Purpose.
+

learn-pr/wwl-azure/design-data-storage-solution-for-relational-data/includes/5-recommend-database-scalability.md

@@ -34,6 +34,6 @@ Review the following scaling scenarios, and think about which database scaling s
 
 | Scenario | Scaling solution |
 | --- | --- |
-| Manage and scale multiple Azure SQL databases that have varying and unpredictable resource requirements | **Elastic database pools and vertical scaling**. Use elastic database pools to ensure databases get the performance resources they need when they need it. Elastic pools provide a simple resource allocation mechanism within a predictable budget. There's no per-database charge for elastic pools. You're billed for each hour a pool exists at the highest eDTU or vCores, regardless of usage or whether the pool was active for less than an hour. |
-| Different sections of a database reside in different geographic locations for compliance reasons | **Horizontal scaling and sharding**. Use sharding to split your data into several databases and scale them independently. The shard map manager is a special database that maintains global mapping information about all shards (databases) in a shard set. The metadata allows an application to connect to the correct database based on the value of the sharding key. |
-| Dependency support for commercial BI or data integration tools, where multiple databases contribute rows into a single overall result for use in Excel, Power BI, or Tableau | **Elastic database tools and elastic query**. Use the Elastic database tools elastic query feature to access data spread across multiple databases. Elastic query is available on the Standard tier. Querying can be done in T-SQL that spans multiple databases in Azure SQL Database. Run cross-database queries to access remote tables, and to connect tools (Excel, Power BI, Tableau, and so on) and query across data tiers. You can scale out queries to large data tiers and visualize the results in business intelligence reports. |
+| Manage and scale multiple Azure SQL databases that have varying and unpredictable resource requirements | **Elastic database pools and vertical scaling**. Elastic database pools let databases share resources, helping them perform well when needed. You pay a set hourly rate for the pool based on its highest capacity, with no extra charge per database. |
+| Different sections of a database reside in different geographic locations for compliance reasons | **Horizontal scaling and sharding**. Sharding splits data across multiple databases for independent scaling. The shard map manager helps applications find the right database using the sharding key.|
+| Dependency support for commercial BI or data integration tools, where multiple databases contribute rows into a single overall result for use in Excel, Power BI, or Tableau | **Elastic database tools and elastic query**. You can use elastic query to access data across multiple databases in Azure SQL Database. This feature lets you run T-SQL queries on remote tables and connect tools like Excel, Power BI, and Tableau to view and analyze data. Elastic query is available on the Standard tier and supports scalable, cross-database queries for business reporting.|

learn-pr/wwl-azure/design-data-storage-solution-for-relational-data/includes/6-recommend-database-availability.md

@@ -44,7 +44,7 @@ The image illustrates the availability architecture for the vCore Hyperscale tie
 
 - The Hyperscale tier architecture uses paired page servers. You can scale horizontally to put all the data in caching layers.
 
-- The Hyperscale architecture supports databases as large as 100 TB.
+- The Hyperscale architecture supports databases as large as 128 TB.
 
 - This tier uses snapshots, which allow for nearly instantaneous database backups, regardless of database size.
 

learn-pr/wwl-azure/design-data-storage-solution-for-relational-data/includes/7-design-security-for-data-at-rest-data-transmission-data-use.md

@@ -18,20 +18,20 @@ Data exists in three basic states: data at rest, data in motion, and data in pro
 There are different encryption methods for each of data state. The following table summarizes the methods. 
 
 | Data state | Encryption method | Encryption level |
-| --- | --- |
-| **Data at rest** | Transparent data encryption (TDE) | Always encrypted. |
-| **Data in motion** | Secure Socket Layers and Transport Layer Security (SSL/TLS) | Always encrypted. |
-| **Data in process** | Dynamic data masking | Specific data is unencrypted. Remaining data is encrypted. |
+| --- | --- | --- |
+| **Data at rest** | Transparent data encryption (TDE) | Always encrypted. |
+| **Data in motion** | Transport Layer Security (TLS 1.2 or higher) | Always encrypted. |
+| **Data in process** | Dynamic data masking | Specific data is unencrypted. Remaining data is encrypted. |
 
 ### Things to know about data encryption
 
 - Transparent data encryption (TDE) protects Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse Analytics against the threat of malicious offline activity by encrypting data at rest. TDE performs real-time encryption and decryption of the database, associated backups, and transaction log files at rest without requiring changes to the application. TDE is enabled by default to all newly deployed Azure SQL Databases. 
 
-- Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse Analytics enforce Secure Socket Layers and Transport Layer Security (SSL/TLS) encryption always for all connections. This level of encryption ensures all data is encrypted "in transit" between the client and server. Transport Layer Security (TLS) is used by all drivers that Microsoft supplies or supports for connecting to databases in Azure SQL Database or Azure SQL Managed Instance. 
+- Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse Analytics enforce Transport Layer Security (TLS) 1.2 or higher for all connections. TLS 1.0 and TLS 1.1 are retired and no longer supported. This level of encryption ensures all data is encrypted "in transit" between the client and server. Transport Layer Security is used by all drivers that Microsoft supplies or supports for connecting to databases in Azure SQL Database or Azure SQL Managed Instance. 
 
 - Data-in-use employs a policy-based security feature called _dynamic data masking_. This feature hides the sensitive data in the result set of a query over designated database fields, while the data in the database remains unchanged. Dynamic data masking helps prevent unauthorized access to sensitive data by enabling customers to designate how much of the sensitive data to reveal with minimal consequence on the application layer.
 
    :::image type="content" source="../media/dynamic-data-masking.png" alt-text="Diagram shows how parts of a data block are masked." border="false":::
 
 > [!TIP]
-> Expand your learning with the [Plan and implement security for Azure SQL Database and Azure SQL Managed Instance](/training/modules/security-azure-sql-database-azure-sql-managed-instance/) learning module. 
+> Expand your learning with the [Plan and implement security for Azure SQL Database and Azure SQL Managed Instance](/training/modules/security-azure-sql-database-azure-sql-managed-instance/) learning module.