Fix more code blocks 2

markingmyname · markingmyname · commit 8fc981ac3b72 · 2022-03-31T15:53:40.000-05:00
diff --git a/docs/database-engine/service-broker/handling-service-broker-error-messages.md b/docs/database-engine/service-broker/handling-service-broker-error-messages.md
@@ -28,7 +28,7 @@ Service Broker applications can communicate errors by using either system-define
 
 Use the WITH ERROR clause of the END CONVERSATION statement to report application errors that are severe enough to require ending the conversation. For example:
 
-```
+```sql
     END CONVERSATION @ConversationHandle
         WITH ERROR = 1234 DESCRIPTION = "The account specified in the invoice does not exist, verify the account number."
 ```
diff --git a/docs/database-engine/service-broker/how-to-activate-service-broker-message-delivery-in-databases-transact-sql.md b/docs/database-engine/service-broker/how-to-activate-service-broker-message-delivery-in-databases-transact-sql.md
@@ -25,7 +25,7 @@ By default, Service Broker message delivery is active in a database when the dat
 
 ## Example
 
-```
+```sql
     USE master ;
     GO
     
diff --git a/docs/database-engine/service-broker/how-to-activate-service-broker-message-forwarding-transact-sql.md b/docs/database-engine/service-broker/how-to-activate-service-broker-message-forwarding-transact-sql.md
@@ -26,7 +26,7 @@ Message forwarding allows an instance of SQL Server to accept messages from outs
 
 
 
-```
+```sql
     USE master ;
     GO
     
diff --git a/docs/database-engine/service-broker/how-to-activate-service-broker-networking-transact-sql.md b/docs/database-engine/service-broker/how-to-activate-service-broker-networking-transact-sql.md
@@ -29,7 +29,7 @@ Service Broker does not send or receive messages over the network by default. To
 
 
 
-```
+```sql
     USE master;
     GO
     
diff --git a/docs/database-engine/service-broker/how-to-allow-service-broker-network-access-by-using-certificates-transact-sql.md b/docs/database-engine/service-broker/how-to-allow-service-broker-network-access-by-using-certificates-transact-sql.md
@@ -46,7 +46,7 @@ Once access is configured in each instance, then communications between the two
 
 
 
-```
+```sql
     USE master ;
     GO
     
@@ -79,7 +79,6 @@ Once access is configured in each instance, then communications between the two
     BACKUP CERTIFICATE TransportSecurity
         TO FILE = 'C:\Certificates\ThisInstanceCertificate.cer' ;
     GO
-```
 
 ## See Also
 
diff --git a/docs/database-engine/service-broker/how-to-allow-service-broker-network-access-by-using-windows-authentication-transact-sql.md b/docs/database-engine/service-broker/how-to-allow-service-broker-network-access-by-using-windows-authentication-transact-sql.md
@@ -27,12 +27,9 @@ Once access is configured in each instance, then communications between the two
 > [!NOTE]
 > If both instances run as the same domain account, then the instances can always communicate using Windows Authentication for transport security. If the instances run as the **LocalSystem** account, the login name is MachineName$, and Kerberos must be available on the network to use the machine account.
 
-
 ## Example
 
-
-
-```
+```sql
     USE master ;
     GO
     
@@ -49,5 +46,4 @@ Once access is configured in each instance, then communications between the two
 
 [CREATE LOGIN (Transact-SQL)](../../t-sql/statements/create-login-transact-sql.md)
 
-[CREATE USER (Transact-SQL)](../../t-sql/statements/create-user-transact-sql.md)
-
+[CREATE USER (Transact-SQL)](../../t-sql/statements/create-user-transact-sql.md)
diff --git a/docs/database-engine/service-broker/how-to-configure-initiating-services-for-anonymous-dialog-security-transact-sql.md b/docs/database-engine/service-broker/how-to-configure-initiating-services-for-anonymous-dialog-security-transact-sql.md
@@ -38,7 +38,7 @@ This example configures anonymous dialog security for conversations between the
 
 [!INCLUDE [SQL Server Service Broker AdventureWorks2008R2](../../includes/service-broker-adventureworks-2008-r2.md)]
 
-```
+```sql
     USE AdventureWorks2008R2 ;
     GO
     
diff --git a/docs/database-engine/service-broker/how-to-configure-initiating-services-for-full-dialog-security-transact-sql.md b/docs/database-engine/service-broker/how-to-configure-initiating-services-for-full-dialog-security-transact-sql.md
@@ -55,7 +55,7 @@ To make sure that an initiating service uses dialog security, you create a remot
 
 [!INCLUDE [SQL Server Service Broker AdventureWorks2008R2](../../includes/service-broker-adventureworks-2008-r2.md)]
 
-```
+```sql
     USE AdventureWorks2008R2 ;
     GO
     
diff --git a/docs/database-engine/service-broker/how-to-configure-permissions-for-a-local-service-transact-sql.md b/docs/database-engine/service-broker/how-to-configure-permissions-for-a-local-service-transact-sql.md
@@ -32,7 +32,7 @@ This example configures permissions to allow BrokerApplicationUser to send messa
 
 [!INCLUDE [SQL Server Service Broker AdventureWorks2008R2](../../includes/service-broker-adventureworks-2008-r2.md)]
 
-```
+```sql
     USE AdventureWorks2008R2 ;
     GO
     
diff --git a/docs/database-engine/service-broker/how-to-configure-target-services-for-anonymous-dialog-security-transact-sql.md b/docs/database-engine/service-broker/how-to-configure-target-services-for-anonymous-dialog-security-transact-sql.md
@@ -40,7 +40,7 @@ SQL Server uses dialog security for any conversation to a service for which a re
 
 [!INCLUDE [SQL Server Service Broker AdventureWorks2008R2](../../includes/service-broker-adventureworks-2008-r2.md)]
 
-```
+```sql
     USE AdventureWorks2008R2 ;
     GO
     
diff --git a/docs/database-engine/service-broker/how-to-configure-target-services-for-full-dialog-security-transact-sql.md b/docs/database-engine/service-broker/how-to-configure-target-services-for-full-dialog-security-transact-sql.md
@@ -58,7 +58,7 @@ To make sure that a target service uses dialog security, create a user for the i
 
 [!INCLUDE [SQL Server Service Broker AdventureWorks2008R2](../../includes/service-broker-adventureworks-2008-r2.md)]
 
-```
+```sql
     USE AdventureWorks2008R2 ;
     GO
     
diff --git a/docs/database-engine/service-broker/how-to-create-certificates-for-service-broker-transport-security-transact-sql.md b/docs/database-engine/service-broker/how-to-create-certificates-for-service-broker-transport-security-transact-sql.md
@@ -26,7 +26,7 @@ For more information using certificates for Service Broker transport security, s
 
 
 
-```
+```sql
     USE master ;
     GO
     
diff --git a/docs/database-engine/service-broker/how-to-deactivate-service-broker-message-delivery-in-databases-transact-sql.md b/docs/database-engine/service-broker/how-to-deactivate-service-broker-message-delivery-in-databases-transact-sql.md
@@ -28,7 +28,7 @@ When message delivery is not active, messages remain in the transmission queue.
 
 [!INCLUDE [SQL Server Service Broker AdventureWorks2008R2](../../includes/service-broker-adventureworks-2008-r2.md)]
 
-```
+```sql
     USE master ;
     GO
     
diff --git a/docs/database-engine/service-broker/how-to-deactivate-service-broker-message-forwarding-transact-sql.md b/docs/database-engine/service-broker/how-to-deactivate-service-broker-message-forwarding-transact-sql.md
@@ -24,7 +24,7 @@ Message forwarding allows an instance of SQL Server to accept messages from outs
 
 
 
-```
+```sql
     USE master ;
     GO
     
diff --git a/docs/database-engine/service-broker/how-to-deactivate-service-broker-networking-transact-sql.md b/docs/database-engine/service-broker/how-to-deactivate-service-broker-networking-transact-sql.md
@@ -24,7 +24,7 @@ Service Broker sends and receives messages over the network while any Service Br
 
 
 
-```
+```sql
     USE master ;
     GO
     
diff --git a/docs/database-engine/service-broker/how-to-pause-service-broker-networking-transact-sql.md b/docs/database-engine/service-broker/how-to-pause-service-broker-networking-transact-sql.md
@@ -24,7 +24,7 @@ Service Broker sends and receives messages over the network while any endpoint f
 
 
 
-```
+```sql
     USE master ;
     GO
     
diff --git a/docs/database-engine/service-broker/how-to-resume-service-broker-networking-transact-sql.md b/docs/database-engine/service-broker/how-to-resume-service-broker-networking-transact-sql.md
@@ -27,7 +27,7 @@ Service Broker sends and receives messages over the network while any endpoint f
 
 
 
-```
+```sql
     USE master ;
     GO
     
diff --git a/docs/database-engine/service-broker/how-to-retrieve-information-from-a-service-broker-error-message-transact-sql.md b/docs/database-engine/service-broker/how-to-retrieve-information-from-a-service-broker-error-message-transact-sql.md
@@ -36,7 +36,7 @@ A message of type **https://schemas.microsoft.com/SQL/ServiceBroker/Error** is a
 
 
 
-```
+```sql
     -- The variables to hold the error code and the description are
     -- provided by the caller.
     
diff --git a/docs/database-engine/service-broker/managing-conversation-priorities.md b/docs/database-engine/service-broker/managing-conversation-priorities.md
@@ -24,13 +24,13 @@ Conversation priorities are always active for RECEIVE statements. The HONOR_BROK
 
 An administrator can enable conversation priorities for SEND statements in a database by using the following statement:
 
-```
+```sql
     ALTER DATABASE MyDatabase SET HONOR_BROKER_PRIORITY ON;
 ```
 
 An administrator can turn off conversation priorities for SEND statements by using the following statement:
 
-```
+```sql
     ALTER DATABASE MyDatabase SET HONOR_BROKER_PRIORITY OFF;
 ```
 
@@ -46,7 +46,7 @@ Conversation priorities are specified by using the CREATE BROKER PRIORITY, ALTER
 
 Conversation priorities are stored in the **sys.conversation_priorities** system view. The following statement lists all the conversation priorities in the current database:
 
-```
+```sql
     SELECT scp.name AS priority_name,
            ssc.name AS contract_name,
            ssvc.name AS local_service_name,
diff --git a/docs/database-engine/service-broker/querying-queues.md b/docs/database-engine/service-broker/querying-queues.md
@@ -26,13 +26,13 @@ For a description of the columns in a queue, see [CREATE QUEUE (Transact-SQL)](.
 
 Following is an example SELECT statement to find out the number of messages in the queue **ExpenseQueue**:
 
-```
+```sql
     SELECT COUNT(*) FROM dbo.ExpenseQueue WITH (NOLOCK) ;
 ```
 
 The following SELECT statement lets the administrator learn whether the queue **ExpenseQueue** contains any messages for the service **//Adventure-Works.com/AccountsPayable/Expenses**:
 
-```
+```sql
     IF EXISTS(SELECT * FROM dbo.ExpenseQueue WITH (NOLOCK) WHERE
               service_name = '//Adventure-Works.com/AccountsPayable/Expenses')
       PRINT 'The queue contains messages for ' +
diff --git a/docs/database-engine/service-broker/removing-poison-messages.md b/docs/database-engine/service-broker/removing-poison-messages.md
@@ -41,7 +41,7 @@ The following example shows how to inspect a message safely for the conversation
 
 [!INCLUDE [SQL Server Service Broker AdventureWorks2008R2](../../includes/service-broker-adventureworks-2008-r2.md)]
 
-```
+```sql
     use AdventureWorks2008R2 ;
     GO
     
@@ -110,7 +110,7 @@ The following example shows how to inspect a message safely for the conversation
 
 When you find a poison message, you end the conversation. The following example ends the conversation e29059bb-9922-40f4-a575-66b2e4c70cf9.
 
-```
+```sql
     -- End the conversation. Do this only if the message cannot be
     -- processed by the normal procedure.
     
diff --git a/docs/database-engine/service-broker/service-broker-application-outline.md b/docs/database-engine/service-broker/service-broker-application-outline.md
@@ -53,7 +53,7 @@ For simplicity, the script produces a result set for each message. If an error o
 
 [!INCLUDE [SQL Server Service Broker AdventureWorks2008R2](../../includes/service-broker-adventureworks-2008-r2.md)]
 
-```
+```sql
     USE AdventureWorks2008R2 ;
     GO
     
diff --git a/docs/database-engine/service-broker/service-script-example.md b/docs/database-engine/service-broker/service-script-example.md
@@ -24,7 +24,7 @@ This Transact-SQL code sample defines a service that archives untyped XML docume
 
 [!INCLUDE [SQL Server Service Broker AdventureWorks2008R2](../../includes/service-broker-adventureworks-2008-r2.md)]
 
-```
+```sql
     -- The contract script contains definitions that must be
     -- present for both the intiating service and the target
     -- service.
@@ -67,7 +67,7 @@ This Transact-SQL code sample defines a service that archives untyped XML docume
 
 ## Service Definition Script
 
-```
+```sql
     -- This script defines the target service. The
     -- objects created by this script are only
     -- required in a database that hosts the target
diff --git a/docs/database-engine/service-broker/starting-and-stopping-the-queue.md b/docs/database-engine/service-broker/starting-and-stopping-the-queue.md
@@ -18,7 +18,7 @@ Use the ALTER QUEUE statement to start and stop a queue. When a queue is started
 
 Administrators often create queues in an unavailable state. This prevents Service Broker from placing messages on the queue until all of the objects for a service are created. When the service is ready to receive messages, the administrator makes the queue available with the following statement:
 
-```
+```sql
     ALTER QUEUE dbo.ExpenseQueue WITH STATUS = ON ;
 ```
 
diff --git a/docs/database-engine/service-broker/troubleshooting-conversation-priorities.md b/docs/database-engine/service-broker/troubleshooting-conversation-priorities.md
@@ -22,7 +22,7 @@ This topic provides suggestions for correcting common symptoms related to Servic
 
 Use the **sys.databasesis_broker_priority_honored** column to determine the state of the HONOR_BROKER_PRIORITY database option:
 
-```
+```sql
     SELECT name AS database_name,
            CASE is_broker_priority_honored
                 WHEN 0 THEN N'OFF'
diff --git a/docs/database-engine/service-broker/troubleshooting-routing-and-message-delivery.md b/docs/database-engine/service-broker/troubleshooting-routing-and-message-delivery.md
@@ -28,7 +28,7 @@ If messages are not successfully delivered between two services, use the **ssbdi
 
 Ensure that Service Broker message delivery is activated in the database. The **is_broker_enabled** column of **sys.databases** shows whether broker message delivery is activated, as shown in the following sample:
 
-```
+```sql
     SELECT is_broker_enabled FROM sys.databases
     WHERE database_id = DB_ID() ;
 ```
@@ -122,7 +122,7 @@ For more information about retries, see [Service Broker Routing and Networking](
 
 Ensure that the service name specified in the message exactly matches the service name specified in the route. Service Broker uses a byte-by-byte binary comparison to match service names. If a route that specifies the service name exists, you can compare the names by running the following query:
 
-```
+```sql
     SELECT N'No Exact Match' = tq.to_service_name
     FROM sys.transmission_queue AS tq
     WHERE NOT EXISTS
diff --git a/docs/database-engine/service-broker/understanding-collation-and-service-broker.md b/docs/database-engine/service-broker/understanding-collation-and-service-broker.md
@@ -26,7 +26,7 @@ Queues use a consistent collation regardless of the default collation of the SQL
 
 For example, an application that uses message retention may need to preserve some messages for a conversation before the application ends the conversation. The following Transact-SQL code sample saves all messages, for a given conversation, that have a message type name in the table **AuditedMessageTypes**.
 
-```
+```sql
     IF @messageTypeName =
       'https://schemas.microsoft.com/SQL/ServiceBroker/EndDialog'
     BEGIN

-Original file line number
+Diff line change
 -```
 +```sql
     USE master ;
     GO