Merge pull request #21666 from v-rajagt/maghan-4

Link fixed.

Author: PRMerger5

docs/database-engine/service-broker/broker-system-messages.md

@@ -24,9 +24,9 @@ In addition to the application-defined message types specified in the contract,
 
 ## Error Messages
 
-When a remote service ends a dialog with an error or the local broker detects an unrecoverable error in a dialog, the local broker creates an Error Message. Error messages are of message type **https://schemas.microsoft.com/SQL/ServiceBroker/Error**. Error messages are validated as well-formed XML.
+When a remote service ends a dialog with an error or the local broker detects an unrecoverable error in a dialog, the local broker creates an Error Message. Error messages are of message type `https://schemas.microsoft.com/SQL/ServiceBroker/Error`. Error messages are validated as well-formed XML.
 
-The XML document that is contained in an error message uses the namespace **https://schemas.microsoft.com/SQL/ServiceBroker**. The root element of the document has the local name **Error**, and contains an element named **Code** and an element named **Message**. The **Code** element holds an integer value. The **Message** element holds the human-readable text of the message.
+The XML document that is contained in an error message uses the namespace `https://schemas.microsoft.com/SQL/ServiceBroker`. The root element of the document has the local name **Error**, and contains an element named **Code** and an element named **Message**. The **Code** element holds an integer value. The **Message** element holds the human-readable text of the message.
 
 For example, an error message generated by a service that processes expense reports might contain the following XML (reformatted for readability):
 
@@ -47,13 +47,13 @@ When an error message arrives for a dialog, the broker raises an error if an app
 
 ## End Dialog Messages
 
-When an application ends a dialog without specifying an error, the local broker sends an End Dialog message to the remote broker. End Dialog messages are of message type **https://schemas.microsoft.com/SQL/ServiceBroker/EndDialog**.
+When an application ends a dialog without specifying an error, the local broker sends an End Dialog message to the remote broker. End Dialog messages are of message type `https://schemas.microsoft.com/SQL/ServiceBroker/EndDialog`.
 
 End Dialog messages are empty messages. A receive operation receives an End Dialog message in the order in which the message arrived on the queue.
 
 ## Dialog Timer Messages
 
-Dialog timer messages indicate that the conversation timer on a dialog has expired. These messages are of message type **https://schemas.microsoft.com/SQL/ServiceBroker/DialogTimer**. A conversation timer is specific to one side of the conversation; Service Broker never sends a dialog timer message to the other side of the conversation.
+Dialog timer messages indicate that the conversation timer on a dialog has expired. These messages are of message type `https://schemas.microsoft.com/SQL/ServiceBroker/DialogTimer`. A conversation timer is specific to one side of the conversation; Service Broker never sends a dialog timer message to the other side of the conversation.
 
 Dialog timer messages are empty messages. A receive operation receives the dialog timer message before any other message for that dialog, regardless of the order in which the time-out message arrived on the queue.
 
@@ -65,4 +65,4 @@ Dialog timer messages are empty messages. A receive operation receives the dialo
 - [CREATE CONTRACT (Transact-SQL)](../../t-sql/statements/create-contract-transact-sql.md)
 - [CREATE MESSAGE TYPE (Transact-SQL)](../../t-sql/statements/create-message-type-transact-sql.md)
 - [END CONVERSATION (Transact-SQL)](../../t-sql/statements/end-conversation-transact-sql.md)
-- [RECEIVE (Transact-SQL)](../../t-sql/statements/receive-transact-sql.md)
+- [RECEIVE (Transact-SQL)](../../t-sql/statements/receive-transact-sql.md)

docs/database-engine/service-broker/creating-a-remote-service-binding.md

@@ -23,7 +23,7 @@ When a conversation is initiated, Service Broker checks to see whether a remote
 
 ## Requesting Remote Service Binding
 
-Requests for remote service bindings use the message type **https://schemas.microsoft.com/SQL/ServiceBroker/BrokerConfigurationNotice/MissingRemoteServiceBinding**. The message is in XML format, and contains the name of the service for which remote service binding information should be available.
+Requests for remote service bindings use the message type `https://schemas.microsoft.com/SQL/ServiceBroker/BrokerConfigurationNotice/MissingRemoteServiceBinding`. The message is in XML format, and contains the name of the service for which remote service binding information should be available.
 
 For example, the following message is a request for a remote service binding to the service **http://Adventure-Works.com/Elsewhere**:
 
@@ -42,4 +42,4 @@ In either case, the application ends the conversation. Service Broker sends one
 ## See also
 
 - [CREATE REMOTE SERVICE BINDING (Transact-SQL)](../../t-sql/statements/create-remote-service-binding-transact-sql.md)
-- [Service Broker Configuration Notice Service](service-broker-configuration-notice-service.md)
+- [Service Broker Configuration Notice Service](service-broker-configuration-notice-service.md)

docs/database-engine/service-broker/creating-service-broker-objects.md

@@ -48,7 +48,7 @@ To create the objects for a service, do the following:
 
 4. Create a service. The service definition specifies the queue that the service uses and the contracts for which this service is the target.
 
-In most cases, you create the target service and then use the contracts and message types created for the target service to create an initiating service. In some cases, however, you may create a target service for an initiating service that is already defined. In these cases, the target service uses the message types and contracts that the initiating service uses. For example, if you are creating a target service to receive event notifications, you use the contract **https://schemas.microsoft.com/SQL/Notifications/PostEventNotification**, because this is the contract that the initiating service uses.
+In most cases, you create the target service and then use the contracts and message types created for the target service to create an initiating service. In some cases, however, you may create a target service for an initiating service that is already defined. In these cases, the target service uses the message types and contracts that the initiating service uses. For example, if you are creating a target service to receive event notifications, you use the contract `https://schemas.microsoft.com/SQL/Notifications/PostEventNotification`, because this is the contract that the initiating service uses.
 
 ## Managing Object Definitions
 
@@ -81,4 +81,4 @@ If your application involves sending messages between SQL Server instances, it i
 - [Contracts](contracts.md)
 - [Queues](queues.md)
 - [Message Types](message-types.md)
-- [Service Broker Routing](service-broker-routing.md)
+- [Service Broker Routing](service-broker-routing.md)

docs/database-engine/service-broker/dialog-conversations.md

@@ -45,7 +45,7 @@ Applications are responsible for indicating when they are finished with a dialog
 
 A conversation timer allows an application to receive a message at a specific time. When the conversation timer expires, SQL Server inserts a message for the conversation into the queue for the conversation, at the endpoint that started the conversation timer. An application can use a conversation timer for any purpose. One common use for a conversation timer is to respond to delays in responses from the remote service. Another common use is to create a service that sends messages to the remote service at set intervals. For example, a service might use a conversation timer to report on the current state of SQL Server every few minutes. Applications can also use a conversation timer to activate a stored procedure at a certain time. This allows Service Broker to support scheduled activities.
 
-Each participant in a conversation can set one conversation timer per conversation. The conversation timer is not shared with the other participant, and the conversation timer does not affect the lifetime of the conversation. Instead, when the timer expires, the local Service Broker adds a time-out message to the queue for the local service. A time-out message has the type name **https://schemas.microsoft.com/SQL/ServiceBroker/DialogTimer**
+Each participant in a conversation can set one conversation timer per conversation. The conversation timer is not shared with the other participant, and the conversation timer does not affect the lifetime of the conversation. Instead, when the timer expires, the local Service Broker adds a time-out message to the queue for the local service. A time-out message has the type name `https://schemas.microsoft.com/SQL/ServiceBroker/DialogTimer`
 
 ## See also
 
@@ -55,4 +55,4 @@ Each participant in a conversation can set one conversation timer per conversati
 - [SEND (Transact-SQL)](../../t-sql/statements/send-transact-sql.md)
 - [RECEIVE (Transact-SQL)](../../t-sql/statements/receive-transact-sql.md)
 - [sys.transmission_queue (Transact-SQL)](../../relational-databases/system-catalog-views/sys-transmission-queue-transact-sql.md)
-- [Broker System Messages](broker-system-messages.md)
+- [Broker System Messages](broker-system-messages.md)

docs/database-engine/service-broker/handling-service-broker-error-messages.md

@@ -33,7 +33,7 @@ Use the WITH ERROR clause of the END CONVERSATION statement to report applicatio
 
 The END CONVERSATION WITH ERROR statement:
 
-- Generates a Service Broker system error message and sends it to the remote side of the conversation. The error messages use the system-defined **https://schemas.microsoft.com/SQL/ServiceBroker/Error** message type.
+- Generates a Service Broker system error message and sends it to the remote side of the conversation. The error messages use the system-defined `https://schemas.microsoft.com/SQL/ServiceBroker/Error` message type.
 
 - Ends the local side of the conversation.
 
@@ -63,15 +63,15 @@ Application code receiving messages from Service Broker conversations must have
 
 - Error messages generated by an application that uses an application-defined error message type.
 
-- Error messages generated by an application that uses the WITH ERROR clause of the END CONVERSATION statement. These error messages use the **https://schemas.microsoft.com/SQL/ServiceBroker/Error** message type and have a positive number in the **Code** element.
+- Error messages generated by an application that uses the WITH ERROR clause of the END CONVERSATION statement. These error messages use the `https://schemas.microsoft.com/SQL/ServiceBroker/Error` message type and have a positive number in the **Code** element.
 
-- Error messages generated by Service Broker. These error messages use the **https://schemas.microsoft.com/SQL/ServiceBroker/Error** message type and have a negative number in the **Code** element. Service Broker creates an **Error** message when an error makes it impossible for Service Broker to continue the conversation. For example, Service Broker cannot locate the destination service because the service does not exist in the current instance and there is no entry for the service in the routing table. In this situation, Service Broker creates an **Error** message for the conversation.
+- Error messages generated by Service Broker. These error messages use the `https://schemas.microsoft.com/SQL/ServiceBroker/Error` message type and have a negative number in the **Code** element. Service Broker creates an **Error** message when an error makes it impossible for Service Broker to continue the conversation. For example, Service Broker cannot locate the destination service because the service does not exist in the current instance and there is no entry for the service in the routing table. In this situation, Service Broker creates an **Error** message for the conversation.
 
 The result set returned by the RECEIVE statement contains a **message_type_name** column. Code that receives Service Broker messages typically uses **message_type_name** to route each message to code that processes the associated message type.
 
 The exact logic a program follows to handle the error depends on the application. One example is a program that uses message retention and requires compensating transactions when the task fails. When an error is received, the program queries the queue for the messages that have already been processed, performs compensating transactions, and then ends the conversation. In contrast, if the program only has to record that an error occurred, the program logs the error to a logging table and ends the conversation.
 
-The **Code** element of the **https://schemas.microsoft.com/SQL/ServiceBroker/Error** message contains the error code. **Error** messages created by an application that uses END CONVERSATION WITH ERROR have a positive value for the error code. **Error** messages generated by Service Broker contain negative values for the error code. The **Code** value in messages generated by Service Broker is just the negated value of the error that caused the **Error** message. For example, when an XML validation error (error code 9615) occurs, the Database Engine creates an **Error** message that has a **Code** element that contains the value **-9615**.
+The **Code** element of the `https://schemas.microsoft.com/SQL/ServiceBroker/Error` message contains the error code. **Error** messages created by an application that uses END CONVERSATION WITH ERROR have a positive value for the error code. **Error** messages generated by Service Broker contain negative values for the error code. The **Code** value in messages generated by Service Broker is just the negated value of the error that caused the **Error** message. For example, when an XML validation error (error code 9615) occurs, the Database Engine creates an **Error** message that has a **Code** element that contains the value **-9615**.
 
 Once an application receives an **Error** message, the program can no longer send messages on that conversation. The application handles the error and then ends its side of the conversation. If an application receives an application-defined error message type, the conversation is still available unless the remote part of the application also ran END CONVERSATION.
 
@@ -83,4 +83,4 @@ Error handling routines should be coded in such a way as to prevent poison messa
 - [CREATE MESSAGE TYPE (Transact-SQL)](../../t-sql/statements/create-message-type-transact-sql.md)
 - [END CONVERSATION (Transact-SQL)](../../t-sql/statements/end-conversation-transact-sql.md)
 - [RECEIVE (Transact-SQL)](../../t-sql/statements/receive-transact-sql.md)
-- [Broker System Messages](broker-system-messages.md)
+- [Broker System Messages](broker-system-messages.md)

docs/database-engine/service-broker/how-to-retrieve-information-from-a-service-broker-error-message-transact-sql.md

@@ -14,7 +14,7 @@ ms.date: "03/30/2022"
 
 [!INCLUDE [sql-asdbmi](../../includes/applies-to-version/sql-asdbmi.md)]
 
-A message of type **https://schemas.microsoft.com/SQL/ServiceBroker/Error** is a Service Broker error message. Messages of this type are XML documents that contain a numeric code for the error and a description of the error.
+A message of type `https://schemas.microsoft.com/SQL/ServiceBroker/Error` is a Service Broker error message. Messages of this type are XML documents that contain a numeric code for the error and a description of the error.
 
 ## To retrieve the information from a Service Broker error message
 

docs/database-engine/service-broker/service-broker-dynamic-routing.md

@@ -24,9 +24,9 @@ When Service Broker cannot find a route for a conversation, Service Broker check
 
 ## Creating the Broker Configuration Notice Service
 
-To create a service for dynamic routing, create a service named **SQL/ServiceBroker/BrokerConfiguration** that accepts conversations on the contract **https://schemas.microsoft.com/SQL/ServiceBroker/BrokerConfigurationNotice**. You then create a route to the service in the routing table for database that will use dynamic routing.
+To create a service for dynamic routing, create a service named **SQL/ServiceBroker/BrokerConfiguration** that accepts conversations on the contract `https://schemas.microsoft.com/SQL/ServiceBroker/BrokerConfigurationNotice`. You then create a route to the service in the routing table for database that will use dynamic routing.
 
-Requests for routes use the message type **https://schemas.microsoft.com/SQL/ServiceBroker/BrokerConfigurationNotice/MissingRoute**. The message is in XML format, and contains the name of the service for which routing information should be available.
+Requests for routes use the message type `https://schemas.microsoft.com/SQL/ServiceBroker/BrokerConfigurationNotice/MissingRoute`. The message is in XML format, and contains the name of the service for which routing information should be available.
 
 For example, the following message is a request for a route to the service http://Adventure-Works.com/Elsewhere:
 
@@ -48,4 +48,4 @@ Notice that, in either case, the application that implements the Broker Configur
 
 ## See also
 
-- [Service Broker Routing](service-broker-routing.md)
+- [Service Broker Routing](service-broker-routing.md)