Light freshness - SQL - Service Broker

Author: gitName

docs/database-engine/service-broker/administration.md

@@ -1,10 +1,10 @@
 ---
-title: Administration (Service Broker)
+title: "Administration (Service Broker)"
 description: "This section describes the tasks that are involved in administering a database that hosts a Service Broker application."
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: mikeray, maghan
-ms.date: "03/30/2022"
+ms.date: 08/29/2025
 ms.service: sql
 ms.subservice: configuration
 ms.topic: reference
@@ -16,26 +16,17 @@ ms.topic: reference
 
 This section describes the tasks that are involved in administering a database that hosts a Service Broker application. Most administrative tasks are part of the regular administration for the database. This section describes how to install and manage applications, establish Service Broker identities, and monitor and troubleshoot the queues. It also describes performance and security issues.
 
-## In This Section
+## In this section
 
-- [Managing Service Broker Applications](managing-service-broker-applications.md)  
-    Describes the tasks that are required to install, maintain, and uninstall Service Broker applications.
+| Article | Description |
+| --- | --- |
+| [Managing Service Broker Applications](managing-service-broker-applications.md) | Describes the tasks that are required to install, maintain, and uninstall Service Broker applications. |
+| [Managing Service Broker Identities](managing-service-broker-identities.md) | Describes how Service Broker identities protect against message misdirection. |
+| [Managing Queues and Messages](managing-queues-and-messages.md) | Describes how an administrator works with queues and messages. |
+| [Managing Forwarding (Service Broker)](managing-forwarding.md) | Describes administrative considerations to manage a database that provides Service Broker message forwarding. |
+| [Managing Security (Service Broker)](managing-security.md) | Describes administrative considerations to manage the security for a Service Broker application. |
+| [Managing Routing](managing-routing.md) | Describes considerations to manage routing. |
 
-- [Managing Service Broker Identities](managing-service-broker-identities.md)  
-    Describes how Service Broker identities protect against message misdirection.
-
-- [Managing Queues and Messages](managing-queues-and-messages.md)  
-    Describes how an administrator works with queues and messages.
-
-- [Managing Forwarding (Service Broker)](managing-forwarding.md)  
-    Describes administrative considerations to manage a database that provides Service Broker message forwarding.
-
-- [Managing Security (Service Broker)](managing-security.md)  
-    Describes administrative considerations to manage the security for a Service Broker application.
-
-- [Managing Routing](managing-routing.md)  
-    Describes considerations to manage routing.
-
-## See also
+## Related content
 
 - [Performance (Service Broker)](performance.md)

docs/database-engine/service-broker/backing-up-and-restoring-service-broker-applications.md

@@ -1,26 +1,26 @@
 ---
-title: Backing Up and Restoring Service Broker Applications
+title: Back Up and Restore Service Broker Applications
 description: "Backup and restore procedures for a Service Broker service are integrated with the database in which the service runs."
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: mikeray, maghan
-ms.date: "03/30/2022"
+ms.date: 08/29/2025
 ms.service: sql
 ms.subservice: configuration
 ms.topic: conceptual
 ---
 
-# Backing Up and Restoring Service Broker Applications
+# Back up and restore Service Broker applications
 
 [!INCLUDE [sql-asdbmi](../../includes/applies-to-version/sql-asdbmi.md)]
 
-Backup and restore procedures for a Service Broker service are integrated with the database in which the service runs. If the service contains components outside the database, such as an external application, you must back up and restore those components separately.
+Backup and restore procedures for a Service Broker service are integrated with the database in which the service runs. If the service contains components outside the database such as an external application, you must back up and restore those components separately.
 
-The **msdb** database contains routes for incoming messages. Therefore, these routes are not backed up with the database that contains the service. Service Broker endpoints and configuration for transport security are stored in the **master** database, so these objects also are not backed up with the database that contains the service.
+The `msdb` database contains routes for incoming messages. Therefore, these routes aren't backed up with the database that contains the service. Service Broker endpoints and configuration for transport security are stored in the `master` database, so these objects also aren't backed up with the database that contains the service.
 
-Service Broker routing relies on a unique identifier in each database to correctly deliver messages. When restoring a backup that is intended to replace the original database, ensure that this identifier is not changed. When restoring a copy of a database to a different location, take care to change this identifier. For more information on Service Broker database identities, see [Managing Service Broker Identities](managing-service-broker-identities.md).
+Service Broker routing relies on a unique identifier in each database to correctly deliver messages. When restoring a backup that is intended to replace the original database, ensure that this identifier isn't changed. When restoring a copy of a database to a different location, take care to change this identifier. For more information on Service Broker database identities, see [Managing Service Broker Identities](managing-service-broker-identities.md).
 
-## See also
+## Related content
 
 - [Migration (Service Broker)](migration.md)
-- [Back Up and Restore of SQL Server Databases](../../relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md)
+- [Back up and restore of SQL Server databases](../../relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md)

docs/database-engine/service-broker/benefits-of-programming-with-service-broker.md

@@ -4,36 +4,36 @@ description: "Queuing and asynchronous messaging are needed for many database ap
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: mikeray, maghan
-ms.date: "03/30/2022"
+ms.date: 08/29/2025
 ms.service: sql
 ms.subservice: configuration
 ms.topic: conceptual
 ---
 
-# Benefits of Programming with Service Broker
+# Benefits of programming with Service Broker
 
 [!INCLUDE [sql-asdbmi](../../includes/applies-to-version/sql-asdbmi.md)]
 
-Queuing and asynchronous messaging are needed for many database applications today. Service Broker provides a new, queue-based durable messaging framework to address these needs. Using the Transact-SQL API provided by Service Broker, you can easily develop services to handle application requirements for queuing or asynchronous communications.
+Queuing and asynchronous messaging are needed for many database applications today. Service Broker provides a queue-based durable messaging framework to address these needs. Using the Transact-SQL API provided by Service Broker, you can easily develop services to handle application requirements for queuing or asynchronous communications.
 
 Some of the benefits of programming with Service Broker are:
 
-- **Flexible development:** The programs used in a single distributed application can be written in multiple languages. Each program provides the functionality of each distributed application component.
+- **Flexible development:** You can write the programs used in a single distributed application in multiple languages. Each program provides the functionality of each distributed application component.
 
-- **Improved security:** You can express security requirements via certificates, so application components do not need to share the same security context. Service Broker uses SQL Server security features to help you secure your applications.
+- **Improved security:** You can express security requirements via certificates, so application components don't need to share the same security context. Service Broker uses SQL Server security features to help you secure your applications.
 
 - **Transactional processing:** Message processing occurs within SQL Server transactions to ensure data integrity. Service Broker supports remote transactional messaging over a standard connection to the database.
 
-- **Guaranteed ordering:** Service Broker provides strong guarantees regarding the delivery and processing of a related set of messages exactly once and in order, so no additional coding is required to provide this functionality.
+- **Guaranteed ordering:** Service Broker provides strong guarantees regarding the delivery and processing of a related set of messages exactly once and in order, so there's no additional coding required to provide this functionality.
 
-- **Reliable delivery:** All of the data needed for a conversation--a set of related communications between two or more services--is persisted in SQL Server. Service Broker supports clustering and database mirroring. A conversation may be maintained through system restarts, server failover, network outages, and so on without failing or losing data.
+- **Reliable delivery:** All of the data needed for a conversation, or a set of related communications between two or more services, is persisted in SQL Server. Service Broker supports clustering and database mirroring. A conversation can be maintained through system restarts, server failover, network outages, and so on without failing or losing data.
 
 - **Improved scalability:** Service Broker routing delivers messages based on the name of the service, rather than on the network address of the computer where the service runs. This allows you to install an application on multiple computers without changing application code.
 
-- **Ability to use existing knowledge:** Service Broker uses Transact-SQL to create objects. Applications that use Service Broker are most often implemented in Transact-SQL or Microsoft .NET Framework-compatible languages. You do not have to learn a new language to create Service Broker applications.
+- **Ability to use existing knowledge:** Service Broker uses Transact-SQL to create objects. Applications that use Service Broker are most often implemented in Transact-SQL or Microsoft .NET Framework-compatible languages. You don't have to learn a new language to create Service Broker applications.
 
-## See also
+## Related content
 
-- [Creating Service Broker Objects](creating-service-broker-objects.md)
+- [Create Service Broker objects](creating-service-broker-objects.md)
 - [Overview (Service Broker)](overview.md)
-- [Creating Service Broker Applications](creating-service-broker-applications.md)
+- [Create Service Broker applications](creating-service-broker-applications.md)

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

@@ -4,25 +4,25 @@ description: "Service Broker uses three system message types to communicate stat
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: mikeray, maghan
-ms.date: "03/30/2022"
+ms.date: 08/29/2025
 ms.service: sql
 ms.subservice: configuration
 ms.topic: reference
 ---
 
-# Broker System Messages
+# Broker system messages
 
 [!INCLUDE [sql-asdbmi](../../includes/applies-to-version/sql-asdbmi.md)]
 
 Service Broker uses three system message types to communicate status and error information from Service Broker.
 
-## Handling System Messages
+## Handle system messages
 
-Most of the messages in a Service Broker conversation are the application-defined messages used to communicate between services. Each message must comply with a message type format that was defined by a CREATE MESSAGE TYPE statement. The set of message types allowed for a conversation is defined by the contract specified in the BEGIN DIALOG CONVERSATION statement.
+Most of the messages in a Service Broker conversation are the application-defined messages used to communicate between services. Each message must comply with a message-type format that was defined by a `CREATE MESSAGE TYPE` statement. The set of message types allowed for a conversation is defined by the contract specified in the `BEGIN DIALOG CONVERSATION` statement.
 
-In addition to the application-defined message types specified in the contract, any conversation can also receive messages that use one of three system-defined message types. These message types are used by Service Broker to report errors and the status of dialogs. Every application must contain logic to handle Error messages and End Dialog messages. If the application sets a conversation timer on a dialog conversation, the application must contain logic to handle Dialog Timer messages. Service Broker provides these message types to every service, whether they appear in the contract for the service or not. For more information, see [Handling Service Broker Error Messages](handling-service-broker-error-messages.md).
+In addition to the application-defined message types specified in the contract, any conversation can also receive messages that use one of three system-defined message types. Service Broker uses these message types to report errors and the status of dialogs. Every application must contain logic to handle Error messages and End Dialog messages. If the application sets a conversation timer on a dialog conversation, the application must contain logic to handle Dialog Timer messages. Service Broker provides these message types to every service, whether they appear in the contract for the service or not. For more information, see [Handle Service Broker error messages](handling-service-broker-error-messages.md).
 
-## Error Messages
+## 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.
 
@@ -45,19 +45,19 @@ A receive operation receives an error message before any message for that dialog
 
 When an error message arrives for a dialog, the broker raises an error if an application tries to send a message on that dialog. However, an application can receive any remaining messages for the dialog, even after it receives an error message.
 
-## End Dialog Messages
+## 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`.
 
 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
 
 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.
+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 timeout message arrived on the queue.
 
-## See also
+## Related content
 
 - [How to: Retrieve Information from a Service Broker Error Message (Transact SQL)](how-to-retrieve-information-from-a-service-broker-error-message-transact-sql.md)
 - [BEGIN CONVERSATION TIMER (Transact-SQL)](../../t-sql/statements/begin-conversation-timer-transact-sql.md)