Merge pull request #26944 from MicrosoftDocs/main

5/02 AM Publish

Author: huypub

azure-sql/database/elastic-query-getting-started-vertical.md

@@ -29,7 +29,7 @@ To start with, create two databases, **Customers** and **Orders**, either in the
 
 Execute the following queries on the **Orders** database to create the **OrderInformation** table and input the sample data.
 
-```tsql
+```sql
 CREATE TABLE [dbo].[OrderInformation](
     [OrderID] [int] NOT NULL,
     [CustomerID] [int] NOT NULL
@@ -43,7 +43,7 @@ INSERT INTO [dbo].[OrderInformation] ([OrderID], [CustomerID]) VALUES (564, 8)
 
 Now, execute following query on the **Customers** database to create the **CustomerInformation** table and input the sample data.
 
-```tsql
+```sql
 CREATE TABLE [dbo].[CustomerInformation](
     [CustomerID] [int] NOT NULL,
     [CustomerName] [varchar](50) NULL,
@@ -62,7 +62,7 @@ INSERT INTO [dbo].[CustomerInformation] ([CustomerID], [CustomerName], [Company]
 1. Open SQL Server Management Studio or SQL Server Data Tools in Visual Studio.
 2. Connect to the Orders database and execute the following T-SQL commands:
 
-    ```tsql
+    ```sql
     CREATE MASTER KEY ENCRYPTION BY PASSWORD = '<master_key_password>';
     CREATE DATABASE SCOPED CREDENTIAL ElasticDBQueryCred
     WITH IDENTITY = '<username>',
@@ -77,7 +77,7 @@ INSERT INTO [dbo].[CustomerInformation] ([CustomerID], [CustomerName], [Company]
 
 To create an external data source, execute the following command on the Orders database:
 
-```tsql
+```sql
 CREATE EXTERNAL DATA SOURCE MyElasticDBQueryDataSrc WITH
     (TYPE = RDBMS,
     LOCATION = '<server_name>.database.windows.net',
@@ -90,7 +90,7 @@ CREATE EXTERNAL DATA SOURCE MyElasticDBQueryDataSrc WITH
 
 Create an external table on the Orders database, which matches the definition of the CustomerInformation table:
 
-```tsql
+```sql
 CREATE EXTERNAL TABLE [dbo].[CustomerInformation]
 ( [CustomerID] [int] NOT NULL,
     [CustomerName] [varchar](50) NOT NULL,
@@ -103,7 +103,7 @@ WITH
 
 Once you have defined your external data source and your external tables, you can now use T-SQL to query your external tables. Execute this query on the Orders database:
 
-```tsql
+```sql
 SELECT OrderInformation.CustomerID, OrderInformation.OrderId, CustomerInformation.CustomerName, CustomerInformation.Company
 FROM OrderInformation
 INNER JOIN CustomerInformation

azure-sql/database/elastic-query-getting-started.md

@@ -56,7 +56,7 @@ These are used to connect to the shard map manager and the shards:
 1. Open SQL Server Management Studio or SQL Server Data Tools in Visual Studio.
 2. Connect to ElasticDBQuery database and execute the following T-SQL commands:
 
-    ```tsql
+    ```sql
     CREATE MASTER KEY ENCRYPTION BY PASSWORD = '<master_key_password>';
 
     CREATE DATABASE SCOPED CREDENTIAL ElasticDBQueryCred
@@ -69,7 +69,7 @@ These are used to connect to the shard map manager and the shards:
 ### External data sources
 To create an external data source, execute the following command on the ElasticDBQuery database:
 
-```tsql
+```sql
 CREATE EXTERNAL DATA SOURCE MyElasticDBQueryDataSrc WITH
     (TYPE = SHARD_MAP_MANAGER,
     LOCATION = '<server_name>.database.windows.net',
@@ -84,7 +84,7 @@ CREATE EXTERNAL DATA SOURCE MyElasticDBQueryDataSrc WITH
 ### External tables
 Create an external table that matches the Customers table on the shards by executing the following command on ElasticDBQuery database:
 
-```tsql
+```sql
 CREATE EXTERNAL TABLE [dbo].[Customers]
 ( [CustomerId] [int] NOT NULL,
     [Name] [nvarchar](256) NOT NULL,
@@ -100,7 +100,7 @@ Once you have defined your external data source and your external tables you can
 
 Execute this query on the ElasticDBQuery database:
 
-```tsql
+```sql
 select count(CustomerId) from [dbo].[Customers]
 ```
 

azure-sql/database/resource-limits-vcore-single-databases.md

@@ -4,7 +4,7 @@ description: This page describes some common vCore resource limits for a single
 author: dimitri-furman
 ms.author: dfurman
 ms.reviewer: wiassaf, mathoma
-ms.date: 04/10/2023
+ms.date: 04/27/2023
 ms.service: sql-database
 ms.subservice: service-overview
 ms.topic: reference
@@ -240,8 +240,8 @@ The [serverless compute tier](serverless-tier-overview.md) is currently availabl
 |Max local SSD IOPS <sup>1</sup>|8000 |16,000 |24,000 |32,000 |40,000 |48,000 |56,000 |
 |Max log rate (MBps)|100 |100 |100 |100 |100 |100 |100 |
 |Local read IO latency<sup>2</sup> |1-2 ms|1-2 ms|1-2 ms|1-2 ms|1-2 ms|1-2 ms|1-2 ms|
-|Remote read IO latency<sup>2</sup>|1-5 ms|1-5 ms|1-5 ms|1-5 ms|1-5 ms|1-5 ms|1-5 ms|
-|Write IO latency<sup>2</sup>|3-5 ms|3-5 ms|3-5 ms|3-5 ms|3-5 ms|3-5 ms|3-5 ms|
+|Remote read IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
+|Write IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
 |Storage type|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|
 |Max concurrent workers|200|400|600|800|1000|1200|1400|
 |Max concurrent external connections <sup>4</sup>|20|40|60|80|100|120|140|
@@ -275,8 +275,8 @@ The [serverless compute tier](serverless-tier-overview.md) is currently availabl
 |Max local SSD IOPS <sup>1</sup>|64,000 |72,000 |80,000 |96,000 |128,000 |160,000 |204,800 |
 |Max log rate (MBps)|100 |100 |100 |100 |100 |100 |100 |
 |Local read IO latency<sup>2</sup> |1-2 ms|1-2 ms|1-2 ms|1-2 ms|1-2 ms|1-2 ms|1-2 ms|
-|Remote read IO latency<sup>2</sup>|1-5 ms|1-5 ms|1-5 ms|1-5 ms|1-5 ms|1-5 ms|1-5 ms|
-|Write IO latency<sup>2</sup>|3-5 ms|3-5 ms|3-5 ms|3-5 ms|3-5 ms|3-5 ms|3-5 ms|
+|Remote read IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
+|Write IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
 |Storage type|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|
 |Max concurrent workers|1600|1800|2000|2400|3200|4000|8000|
 |Max concurrent external connections <sup>4</sup>|150|150|150|150|150|150|150|
@@ -310,8 +310,8 @@ The [serverless compute tier](serverless-tier-overview.md) is currently availabl
 |Max local SSD IOPS <sup>1</sup>|14,000|28,000|42,000|44,800|
 |Max log rate (MBps)|100 |100 |100 |100 |
 |Local read IO latency<sup>2</sup> |1-2 ms|1-2 ms|1-2 ms|1-2 ms|
-|Remote read IO latency<sup>2</sup>|1-5 ms|1-5 ms|1-5 ms|1-5 ms|
-|Write IO latency<sup>2</sup>|3-5 ms|3-5 ms|3-5 ms|3-5 ms|
+|Remote read IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
+|Write IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
 |Storage type|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|
 |Max concurrent workers|160|320|480|640|
 |Max concurrent external connections <sup>4</sup>|16|32|48|64|
@@ -348,8 +348,8 @@ SLOs in the Hyperscale premium-series tier use the naming convention `HS_PRMS_`
 |Max local SSD IOPS <sup>1</sup>|8,000|16,000|24,000|32,000|40,000|
 |Max log rate (MBps)|100 |100 |100 |100 |100 |
 |Local read IO latency<sup>2</sup> |1-2 ms|1-2 ms|1-2 ms|1-2 ms|1-2 ms|
-|Remote read IO latency<sup>2</sup>|1-5 ms|1-5 ms|1-5 ms|1-5 ms|1-5 ms|
-|Write IO latency<sup>2</sup>|3-5 ms|3-5 ms|3-5 ms|3-5 ms|3-5 ms|
+|Remote read IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
+|Write IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
 |Storage type|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|
 |Max concurrent workers|200|400|600|800|1000|
 |Max concurrent external connections <sup>4</sup>|20|40|60|80|100|
@@ -385,8 +385,8 @@ SLOs in the Hyperscale premium-series tier use the naming convention `HS_PRMS_`
 |Max local SSD IOPS <sup>1</sup>|48,000|56,000|64,000|72,000|80,000|
 |Max log rate (MBps)|100 |100 |100 |100 |100 |
 |Local read IO latency<sup>2</sup> |1-2 ms|1-2 ms|1-2 ms|1-2 ms|1-2 ms|
-|Remote read IO latency<sup>2</sup>|1-5 ms|1-5 ms|1-5 ms|1-5 ms|1-5 ms|
-|Write IO latency<sup>2</sup>|3-5 ms|3-5 ms|3-5 ms|3-5 ms|3-5 ms|
+|Remote read IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
+|Write IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
 |Storage type|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|
 |Max concurrent workers|1,200|1,400|1,600|1,800|2,000|
 |Max concurrent external connections <sup>4</sup>|120|140|150|150|150|
@@ -420,8 +420,8 @@ SLOs in the Hyperscale premium-series tier use the naming convention `HS_PRMS_`
 |Max local SSD IOPS <sup>1</sup>|96,000|128,000|160,000|320,000|327,680|
 |Max log rate (MBps)|100 |100 |100 |100 |100|
 |Local read IO latency<sup>2</sup> |1-2 ms|1-2 ms|1-2 ms|1-2 ms|1-2 ms|
-|Remote read IO latency<sup>2</sup>|1-5 ms|1-5 ms|1-5 ms|1-5 ms|1-5 ms|
-|Write IO latency<sup>2</sup>|3-5 ms|3-5 ms|3-5 ms|3-5 ms|3-5 ms|
+|Remote read IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
+|Write IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
 |Storage type|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|
 |Max concurrent workers|2,400|3,200|4,000|8,000|12,800|
 |Max concurrent external connections <sup>4</sup>|150|150|150|150|150|
@@ -458,8 +458,8 @@ SLOs in the Premium-series memory optimized tier use the naming convention `HS_M
 |Max local SSD IOPS <sup>1</sup>|10,240|20,480|30,720|40,960|51,200|
 |Max log rate (MBps)|100 |100 |100 |100 |100 |
 |Local read IO latency<sup>2</sup> |1-2 ms|1-2 ms|1-2 ms|1-2 ms|1-2 ms|
-|Remote read IO latency<sup>2</sup>|1-5 ms|1-5 ms|1-5 ms|1-5 ms|1-5 ms|
-|Write IO latency<sup>2</sup>|3-5 ms|3-5 ms|3-5 ms|3-5 ms|3-5 ms|
+|Remote read IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
+|Write IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
 |Storage type|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|
 |Max concurrent workers|200|400|600|800|1000|
 |Max concurrent external connections <sup>4</sup>|20|40|60|80|100|
@@ -495,8 +495,8 @@ SLOs in the Premium-series memory optimized tier use the naming convention `HS_M
 |Max local SSD IOPS <sup>1</sup>|61,440|71,680|81,920|92,160|102,400|
 |Max log rate (MBps)|100 |100 |100 |100 |100 |
 |Local read IO latency<sup>2</sup> |1-2 ms|1-2 ms|1-2 ms|1-2 ms|1-2 ms|
-|Remote read IO latency<sup>2</sup>|1-5 ms|1-5 ms|1-5 ms|1-5 ms|1-5 ms|
-|Write IO latency<sup>2</sup>|3-5 ms|3-5 ms|3-5 ms|3-5 ms|3-5 ms|
+|Remote read IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
+|Write IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
 |Storage type|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|
 |Max concurrent workers|1,200|1,400|1,600|1,800|2,000|
 |Max concurrent external connections <sup>4</sup>|120|140|150|150|150|
@@ -531,8 +531,8 @@ SLOs in the Premium-series memory optimized tier use the naming convention `HS_M
 |Max local SSD IOPS <sup>1</sup>|122,880|163,840|204,800|327,680|
 |Max log rate (MBps)|100 |100 |100 |100 |
 |Local read IO latency<sup>2</sup> |1-2 ms|1-2 ms|1-2 ms|1-2 ms|
-|Remote read IO latency<sup>2</sup>|1-5 ms|1-5 ms|1-5 ms|1-5 ms|
-|Write IO latency<sup>2</sup>|3-5 ms|3-5 ms|3-5 ms|3-5 ms|
+|Remote read IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
+|Write IO latency<sup>2</sup>|1-4 ms|1-4 ms|1-4 ms|1-4 ms|
 |Storage type|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|Multi-tiered<sup>3</sup>|
 |Max concurrent workers|2,400|3,200|4,000|8,000|
 |Max concurrent external connections <sup>4</sup>|150|150|150|150|

azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.yml

@@ -11,7 +11,7 @@ metadata:
   author: dimitri-furman
   ms.author: dfurman
   ms.reviewer: wiassaf, mathoma
-  ms.date: 02/14/2023
+  ms.date: 05/02/2023
 title: Azure SQL Database Hyperscale FAQ
 summary: |
   [!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
@@ -33,7 +33,7 @@ sections:
       - question: |
           What resource types and purchasing models support Hyperscale?
         answer: |
-          The Hyperscale service tier is only available for single databases using the vCore-based purchasing model in Azure SQL Database.  
+          The Hyperscale service tier is only available for single databases using the vCore-based purchasing model in Azure SQL Database. It is not available in the DTU-based purchasing model.
 
       - question: |
           How does the Hyperscale service tier differ from the General Purpose and Business Critical service tiers?

azure-sql/managed-instance/doc-changes-updates-known-issues.md

@@ -206,7 +206,7 @@ Several system views, performance counters, error messages, XEvents, and error l
 
 **Workaround**: Use `sys.databases` view to resolve the actual database name from the physical database name, specified in the form of GUID database identifiers:
 
-```tsql
+```sql
 SELECT name as ActualDatabaseName, physical_database_name as GUIDDatabaseIdentifier 
 FROM sys.databases
 WHERE database_id > 4;

azure-sql/migration-guides/managed-instance/sql-server-to-managed-instance-overview.md

@@ -189,7 +189,7 @@ If you have memory-optimized tables or memory-optimized table types in your on-p
 - Choose the Business Critical tier for your target SQL managed instance that supports In-Memory OLTP.
 - If you want to migrate to the General Purpose tier in Azure SQL Managed Instance, remove memory-optimized tables, memory-optimized table types, and natively compiled SQL modules that interact with memory-optimized objects before migrating your databases. You can use the following T-SQL query to identify all objects that need to be removed before migration to the General Purpose tier:
 
-   ```tsql
+   ```sql
    SELECT * FROM sys.tables WHERE is_memory_optimized=1
    SELECT * FROM sys.table_types WHERE is_memory_optimized=1
    SELECT * FROM sys.sql_modules WHERE uses_native_compilation=1

docs/big-data-cluster/big-data-cluster-key-versions.md

@@ -146,14 +146,14 @@ The main encryption key will be rotated using `azdata bdc kms set –key-provide
 
 The asymmetric key can be seen using the following T-SQL query, with the `sys.asymmetric_keys` system catalog view.
 
-```tsql
+```sql
 USE master;
 select * from sys.asymmetric_keys;
 ```
 
 The asymmetric key will appear with the naming convention "tde_asymmetric_key_\<version\>". The SQL Server administrator can then change the protector of the DEK to the asymmetric key using [ALTER DATABASE ENCRYPTION KEY](../t-sql/statements/alter-database-encryption-key-transact-sql.md). For example, use the following T-SQL command:
 
-```tsql
+```sql
 USE db1;
 ALTER DATABASE ENCRYPTION KEY ENCRYPTION BY SERVER ASYMMETRIC KEY tde_asymmetric_key_0;
 ```

docs/connect/odbc/using-always-encrypted-with-the-odbc-driver.md

@@ -114,7 +114,7 @@ The table below summarizes the behavior of queries, depending on whether Always
 
 The following examples illustrate retrieving and modifying data in encrypted columns. The examples assume a table with the following schema. The SSN and BirthDate columns are encrypted.
 
-```tsql
+```sql
 CREATE TABLE [dbo].[Patients](
  [PatientId] [int] IDENTITY(1,1),
  [SSN] [char](11) COLLATE Latin1_General_BIN2

docs/database-engine/configure-windows/adr-cleaner-retry-timeout-configuration-option.md

@@ -28,7 +28,7 @@ The cleaner is single threaded in SQL Server 2019 and so one SQL Server instance
 
 The following examples sets the cleaner retry timeout.
 
-```tsql
+```sql
 sp_configure 'show advanced options', 1;  
 RECONFIGURE;
 GO 

docs/database-engine/configure-windows/adr-preallocation-factor-server-configuration-option.md

@@ -37,7 +37,7 @@ While the background thread takes workload patterns into consideration, this fac
 
 The following example sets the preallocation factor to 4.
 
-```tsql
+```sql
 sp_configure 'show advanced options', 1;
 RECONFIGURE;
 GO