Merge pull request #17008 from icoric/icoric-patch-7

sql colorizer updates - tsql docs / statements pt.2

Author: denrea

docs/t-sql/statements/create-broker-priority-transact-sql.md

@@ -37,7 +37,6 @@ ms.author: maghan
 ## Syntax  
 
 ```syntaxsql
-  
 CREATE BROKER PRIORITY ConversationPriorityName  
 FOR CONVERSATION  
 [ SET ( [ CONTRACT_NAME = {ContractName | ANY } ]  
@@ -163,7 +162,7 @@ FOR CONVERSATION
 ### A. Assigning a priority level to both directions of a conversation.  
  These two conversation priorities ensure that all operations that use `SimpleContract` between `TargetService` and the `InitiatorAService` are assigned priority level 3.  
 
-```  
+```sql  
 CREATE BROKER PRIORITY InitiatorAToTargetPriority  
     FOR CONVERSATION  
     SET (CONTRACT_NAME = SimpleContract,  
@@ -181,7 +180,7 @@ CREATE BROKER PRIORITY TargetToInitiatorAPriority
 ### B. Setting the priority level for all conversations that use a contract  
  Assigns a priority level of `7` to all operations that use a contract named `SimpleContract`. This assumes that there are no other priorities that specify both `SimpleContract` and either a local or a remote service.  
 
-```  
+```sql 
 CREATE BROKER PRIORITY SimpleContractDefaultPriority  
     FOR CONVERSATION  
     SET (CONTRACT_NAME = SimpleContract,  
@@ -193,7 +192,7 @@ CREATE BROKER PRIORITY SimpleContractDefaultPriority
 ### C. Setting a base priority level for a database.  
  Defines conversation priorities for two specific services, and then defines a conversation priority that will match all other conversation endpoints. This does not replace the default priority, which is always 5, but does minimize the number of items that are assigned the default.  
 
-```  
+```sql 
 CREATE BROKER PRIORITY [//Adventure-Works.com/Expenses/ClaimPriority]  
     FOR CONVERSATION  
     SET (CONTRACT_NAME = ANY,  

docs/t-sql/statements/create-cryptographic-provider-transact-sql.md

@@ -33,8 +33,7 @@ ms.author: vanto
 
 ## Syntax  
 
-```  
-  
+```syntaxsql  
 CREATE CRYPTOGRAPHIC PROVIDER provider_name   
     FROM FILE = path_of_DLL  
 ```  
@@ -67,7 +66,7 @@ CREATE CRYPTOGRAPHIC PROVIDER provider_name
 ## Examples  
  The following example creates a cryptographic provider called `SecurityProvider` in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] from a .dll file. The .dll file is named `c:\SecurityProvider\SecurityProvider_v1.dll` and it is installed on the server. The provider's certificate must first be installed on the server.  
 
-```  
+```sql  
 -- Install the provider  
 CREATE CRYPTOGRAPHIC PROVIDER SecurityProvider  
     FROM FILE = 'C:\SecurityProvider\SecurityProvider_v1.dll';  

docs/t-sql/statements/create-database-audit-specification-transact-sql.md

@@ -35,7 +35,6 @@ ms.author: vanto
 ## Syntax  
 
 ```syntaxsql
-  
 CREATE DATABASE AUDIT SPECIFICATION audit_specification_name  
 {  
     FOR SERVER AUDIT audit_name   
@@ -93,7 +92,7 @@ CREATE DATABASE AUDIT SPECIFICATION audit_specification_name
 ### A. Audit SELECT and INSERT on a table for any database principal 
  The following example creates a server audit called `Payrole_Security_Audit` and then a database audit specification called `Payrole_Security_Audit` that audits `SELECT` and `INSERT` statements by the `dbo` user, for the `HumanResources.EmployeePayHistory` table in the `AdventureWorks2012` database.  
 
-```  
+```sql  
 USE master ;  
 GO  
 -- Create the server audit.  
@@ -120,7 +119,7 @@ GO
 ### B. Audit any DML (INSERT, UPDATE or DELETE) on _all_ objects in the _sales_ schema for a specific database role  
  The following example creates a server audit called `DataModification_Security_Audit` and then a database audit specification called `Audit_Data_Modification_On_All_Sales_Tables` that audits `INSERT`, `UPDATE` and `DELETE` statements by users in a new database role `SalesUK`, for all objects in the `Sales` schema in the `AdventureWorks2012` database.  
 
-```  
+```sql  
 USE master ;  
 GO  
 -- Create the server audit.

docs/t-sql/statements/create-database-encryption-key-transact-sql.md

@@ -102,7 +102,7 @@ For additional examples using TDE, see [Transparent Data Encryption (TDE&#41
 
 The following example creates a database encryption key by using the `AES_256` algorithm, and protects the private key with a certificate named `MyServerCert`.  
 
-```  
+```sql  
 USE AdventureWorks2012;  
 GO  
 CREATE DATABASE ENCRYPTION KEY  

docs/t-sql/statements/create-event-notification-transact-sql.md

@@ -35,7 +35,6 @@ ms.author: maghan
 ## Syntax  
 
 ```syntaxsql
-  
 CREATE EVENT NOTIFICATION event_notification_name   
 ON { SERVER | DATABASE | QUEUE queue_name }   
 [ WITH FAN_IN ]  
@@ -136,18 +135,21 @@ TO SERVICE 'broker_service' , { 'broker_instance_specifier' | 'current database'
 --Create a queue to receive messages.  
 CREATE QUEUE NotifyQueue ;  
 GO  
+
 --Create a service on the queue that references  
 --the event notifications contract.  
 CREATE SERVICE NotifyService  
 ON QUEUE NotifyQueue  
 ([https://schemas.microsoft.com/SQL/Notifications/PostEventNotification]);  
 GO  
+
 --Create a route on the service to define the address   
 --to which Service Broker sends messages for the service.  
 CREATE ROUTE NotifyRoute  
 WITH SERVICE_NAME = 'NotifyService',  
 ADDRESS = 'LOCAL';  
-GO  
+GO 
+
 --Create the event notification.  
 CREATE EVENT NOTIFICATION log_ddl1   
 ON SERVER   
@@ -170,7 +172,7 @@ TO SERVICE 'NotifyService',
 ### C. Getting information about an event notification that is server scoped  
  The following example queries the `sys.server_event_notifications` catalog view for metadata about event notification `log_ddl1` that was created with server scope.  
 
-```  
+```sql  
 SELECT * FROM sys.server_event_notifications  
 WHERE name = 'log_ddl1';  
 ```  

docs/t-sql/statements/create-external-language-transact-sql.md

@@ -22,7 +22,7 @@ Registers external language extensions in the database from the specified file p
 
 ## Syntax
 
-```text
+```syntaxsql
 CREATE EXTERNAL LANGUAGE language_name  
 [ AUTHORIZATION owner_name ]  
 FROM <file_spec> [ ,...2 ]  

docs/t-sql/statements/create-external-library-transact-sql.md

@@ -41,7 +41,7 @@ Uploads R or Python package files to a database from the specified byte stream o
 ::: moniker range=">=sql-server-ver15||>=sql-server-linux-ver15||=sqlallproducts-allversions"
 ## Syntax for SQL Server 2019
 
-```text
+```syntaxsql
 CREATE EXTERNAL LIBRARY library_name  
 [ AUTHORIZATION owner_name ]  
 FROM <file_spec> [ ,...2 ]  
@@ -83,7 +83,7 @@ WITH ( LANGUAGE = <language> )
 ::: moniker range=">=sql-server-2017 <=sql-server-2017||=sqlallproducts-allversions"
 ## Syntax for SQL Server 2017
 
-```text
+```syntaxsql
 CREATE EXTERNAL LIBRARY library_name  
 [ AUTHORIZATION owner_name ]  
 FROM <file_spec> [ ,...2 ]  
@@ -112,7 +112,7 @@ WITH ( LANGUAGE = 'R' )
 ::: moniker range="=azuresqldb-mi-current||=sqlallproducts-allversions"
 ## Syntax for Azure SQL Managed Instance
 
-```text
+```syntaxsql
 CREATE EXTERNAL LIBRARY library_name  
 [ AUTHORIZATION owner_name ]  
 FROM <file_spec> [ ,...2 ]  

docs/t-sql/statements/create-external-table-as-select-transact-sql.md

@@ -31,8 +31,7 @@ monikerRange: ">= aps-pdw-2016 || = azure-sqldw-latest || = sqlallproducts-allve
 
 ## Syntax
 
-```syntaxsql
-  
+```syntaxsql 
 CREATE EXTERNAL TABLE [ [database_name  . [ schema_name ] . ] | schema_name . ] table_name   
     WITH (   
         LOCATION = 'hdfs_folder',  
@@ -203,9 +202,8 @@ To use CREATE EXTERNAL TABLE AS SELECT containing these characters, you must fir
 
  The resulting Hadoop location and file name will be `hdfs:// xxx.xxx.xxx.xxx:5000/files/Customer/ QueryID_YearMonthDay_HourMinutesSeconds_FileIndex.txt.`.
 
-```  
-  
-      -- Example is based on AdventureWorks   
+```sql  
+-- Example is based on AdventureWorks   
 CREATE EXTERNAL TABLE hdfsCustomer  
 WITH (  
         LOCATION='/pdwdata/customer.tbl',  
@@ -221,9 +219,8 @@ WITH (
 > [!NOTE]
 >  This example specifies for 5000. If the port isn't specified, the database uses 8020 as the default port.
 
-```  
-  
-      -- Example is based on AdventureWorks  
+```sql  
+-- Example is based on AdventureWorks  
 CREATE EXTERNAL TABLE dbo.FactInternetSalesNew  
 WITH   
     (   

docs/t-sql/statements/create-index-transact-sql.md

@@ -891,7 +891,7 @@ INSERT INTO Production.UnitMeasure (UnitMeasureCode, Name, ModifiedDate)
 
 The resulting error message is:
 
-```cmd
+```
 Server: Msg 2601, Level 14, State 1, Line 1
 Cannot insert duplicate key row in object 'UnitMeasure' with unique index 'AK_UnitMeasure_Name'. The statement has been terminated.
 ```
@@ -953,7 +953,7 @@ GO
 
 Here are the results of the second `INSERT` statement.
 
-```cmd
+```
 Server: Msg 2601, Level 14, State 1, Line 5
 Cannot insert duplicate key row in object '#Test' with unique index
 'AK_Index'. The statement has been terminated.

docs/t-sql/statements/create-message-type-transact-sql.md

@@ -93,7 +93,7 @@ CREATE MESSAGE TYPE message_type_name
 ### A. Creating a message type containing well-formed XML  
  The following example creates a new message type that contains well-formed XML.  
 
-```  
+```sql  
 CREATE MESSAGE TYPE  
   [//Adventure-Works.com/Expenses/SubmitExpense]  
   VALIDATION = WELL_FORMED_XML ;     
@@ -102,7 +102,7 @@ CREATE MESSAGE TYPE
 ### B. Creating a message type containing typed XML  
  The following example creates a message type for an expense report encoded in XML. The example creates an XML schema collection that holds the schema for a simple expense report. The example then creates a new message type that validates messages against the schema.  
 
-```  
+```sql  
 CREATE XML SCHEMA COLLECTION ExpenseReportSchema AS  
 N'<?xml version="1.0" encoding="UTF-16" ?>  
   <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"  
@@ -141,7 +141,7 @@ N'<?xml version="1.0" encoding="UTF-16" ?>
 ### C. Creating a message type for an empty message  
  The following example creates a new message type with empty encoding.  
 
-```  
+```sql  
 CREATE MESSAGE TYPE  
     [//Adventure-Works.com/Expenses/SubmitExpense]  
     VALIDATION = EMPTY ;  
@@ -150,7 +150,7 @@ CREATE MESSAGE TYPE
 ### D. Creating a message type containing binary data  
  The following example creates a new message type to hold binary data. Because the message will contain data that is not XML, the message type specifies a validation type of `NONE`. Notice that, in this case, the application that receives a message of this type must verify that the message contains data, and that the data is of the type expected.  
 
-```  
+```sql  
 CREATE MESSAGE TYPE  
     [//Adventure-Works.com/Expenses/ReceiptImage]  
     VALIDATION = NONE ;