Merge pull request #26935 from rwestMSFT/rw-0501-t-sql-code-fence

[SCOPED] Correct code fence tag

Author: JamesJBarnett

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/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 

docs/database-engine/configure-windows/polybase-connectivity-configuration-transact-sql.md

@@ -119,22 +119,22 @@ Starting in [!INCLUDE[sssql22-md](../../includes/sssql22-md.md)], Hadoop is no l
 ### A. List all available configuration settings  
  The following example shows how to list all configuration options.  
 
-```tsql  
+```sql  
 EXEC sp_configure;  
 ```  
 
  The result returns the option name followed by the minimum and maximum values for the option. The **config_value** is the value that PolyBase will use when reconfiguration is complete. The **run_value** is the value that is currently being used. The **config_value** and **run_value** are usually the same unless the value is in the process of being changed.  
 
 ### B. List the configuration settings for one configuration name  
 
-```tsql  
+```sql  
 EXEC sp_configure @configname='hadoop connectivity';  
 ```  
 
 ### C. Set Hadoop connectivity  
  This example sets PolyBase to option 7. This option allows PolyBase to create and use external tables on Hortonworks HDP 2.1, 2.2, and 2.3 on Linux and Windows Server, and Azure Blob Storage. For example, SQL could have 30 external tables with 7 of them referencing data on Hortonworks HDP 2.1 on Linux, 4 on Hortonworks HDP 2.2 on Linux, 7 on Hortonworks HDP 2.3 on Linux, and the other 12 referencing Azure Blob Storage.  
 
-```tsql
+```sql
 --Configure external tables to reference data on Hortonworks HDP 2.1, 2.2, and 2.3 on Linux, and Azure Blob Storage  
 
 sp_configure @configname = 'hadoop connectivity', @configvalue = 7;  

docs/relational-databases/backup-restore/backup-encryption.md

@@ -76,7 +76,7 @@ The account that does backup operations on an encrypted database requires specif
 
    The following example grants the appropriate permissions for the certificate. 
 
-   ```tsql
+   ```sql
    USE [master]
    GO
    GRANT VIEW DEFINITION ON CERTIFICATE::[<SERVER_CERT>] TO [<db_account>]