Merge pull request #35169 from ShawnKupfer/WB1930

Light freshness - SQL - Service Broker 4

Author: JillGrant615

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

@@ -35,7 +35,7 @@ For example, the following message is a request for a remote service binding to
 
 The application that's defined in the BCN queue reads a `MissingRemoteServiceBinding` message from the queue. If the application can determine the appropriate user context for the target service, the application creates a remote service binding for the service, then ends the conversation. If the application can't determine the remote service binding for the service, the application ends the conversation with an error.
 
-If the application ended the conversation with an error, Service Broker stores this response for 10 minutes. Service Broker won't send a `MissingRemoteServiceBinding` message for dialogs to the BCN service during this time. If a conversation is started after 10 minutes, Service Broker will send another `MissingRemoteServiceBinding` message to check whether a remote service binding has been created.
+If the application ended the conversation with an error, Service Broker stores this response for 10 minutes. Service Broker doesn't send a `MissingRemoteServiceBinding` message for dialogs to the BCN service during this time. If a conversation is started after 10 minutes, Service Broker will send another `MissingRemoteServiceBinding` message to check whether a remote service binding has been created.
 
 In either case, the application ends the conversation. Service Broker sends one `MissingRemoteServiceBinding` message at a time for a specific service regardless of the number of conversations to the service. Further, Service Broker uses the longest possible timeout for requests to the BCN service. Therefore, if the BCN service doesn't end the conversation, Service Broker doesn't create a new request to the service. If the BCN service didn't create a remote service binding, secure messages (`ENCRYPTION`=`ON`) remain delayed until the conversation lifetime expires. However, nonsecure messages (`ENCRYPTION`=`OFF`) will continue after the BCN service ends the conversation.
 

docs/database-engine/service-broker/determining-the-dialog-security-type.md

@@ -43,9 +43,9 @@ The following table lists the type of dialog security for each valid combination
 
 ## Related content
 
-- [How to: Configure Initiating Services for Anonymous Dialog Security (Transact-SQL)](how-to-configure-initiating-services-for-anonymous-dialog-security-transact-sql.md)
-- [How to: Configure Initiating Services for Full Dialog Security (Transact-SQL)](how-to-configure-initiating-services-for-full-dialog-security-transact-sql.md)
+- [How to: Configure initiating services for anonymous dialog security (Transact-SQL)](how-to-configure-initiating-services-for-anonymous-dialog-security-transact-sql.md)
+- [How to: Configure initiating services for full dialog security (Transact-SQL)](how-to-configure-initiating-services-for-full-dialog-security-transact-sql.md)
 - [How to: Configure Target Services for Anonymous Dialog Security (Transact-SQL)](how-to-configure-target-services-for-anonymous-dialog-security-transact-sql.md)
 - [How to: Configure Target Services for Full Dialog Security (Transact-SQL)](how-to-configure-target-services-for-full-dialog-security-transact-sql.md)
-- [How to: Configure Permissions for a Local Service (Transact-SQL)](how-to-configure-permissions-for-a-local-service-transact-sql.md)
+- [How to: Configure permissions for a local service (Transact-SQL)](how-to-configure-permissions-for-a-local-service-transact-sql.md)
 - [Service Broker Communication Protocols](service-broker-communication-protocols.md)

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

@@ -20,7 +20,7 @@ Error handling in an application that uses Service Broker has two distinct aspec
 
 | Article | Description |
 | --- | --- |
-| [Handling Transact-SQL Errors (Service Broker)](handling-transact-sql-errors.md) | Describes strategies for working with Transact-SQL errors while maintaining transactional messaging. |
+| [Handle Transact-SQL errors (Service Broker)](handling-transact-sql-errors.md) | Describes strategies for working with Transact-SQL errors while maintaining transactional messaging. |
 | [Handle Service Broker error messages](handling-service-broker-error-messages.md) | Describes strategies for handling error messages delivered by Service Broker. |
 | [Handle poison messages](handling-poison-messages.md) | Describes strategies for recovering from poison messages. |
 

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

@@ -1,5 +1,5 @@
 ---
-title: Handling Service Broker Error Messages
+title: Handle Service Broker Error Messages
 description: "Service Broker applications must handle two types of error messages received from conversations: error messages created by an application that uses Service Broker and system messages created by Service Broker."
 author: rwestMSFT
 ms.author: randolphwest
@@ -39,7 +39,7 @@ The `END CONVERSATION WITH ERROR` statement:
 
 The part of the application that receives the `Error` message should do any needed cleanup and end its side of the conversation.
 
-An application can end an active conversation with an error at any time. However, if the remote side of the conversation has already ended the conversation, Service Broker will not send the error message to the remote side. Instead, Service Broker just ends the local side of the conversation and removes all messages for the conversation from the local queue.
+An application can end an active conversation with an error at any time. However, if the remote side of the conversation has already ended the conversation, Service Broker doesn't send the error message to the remote side. Instead, Service Broker just ends the local side of the conversation and removes all messages for the conversation from the local queue.
 
 ### Application-defined error messages
 
@@ -63,7 +63,7 @@ Application code receiving messages from Service Broker conversations must have
 
 - 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 can't locate the destination service because the service doesn't exist in the current instance and there's 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 can't locate the destination service because the service doesn't exist in the current instance and there's 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.
 

docs/database-engine/service-broker/handling-transact-sql-errors.md

@@ -1,26 +1,26 @@
 ---
-title: Handling Transact-SQL Errors (Service Broker)
+title: "Handle Transact-SQL Errors (Service Broker)"
 description: "Two general principles apply when handling Transact-SQL errors in 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: conceptual
 ---
 
-# Handling Transact-SQL Errors (Service Broker)
+# Handle Transact-SQL errors (Service Broker)
 
 [!INCLUDE [sql-asdbmi](../../includes/applies-to-version/sql-asdbmi.md)]
 
 Two general principles apply when handling Transact-SQL errors in a Service Broker application.
 
-First, an application should not permanently remove a message from a queue without acting upon the message. In most cases, this means that an application should always receive a message within a transaction.
+First, an application shouldn't permanently remove a message from a queue without acting upon the message. In most cases, this means that an application should always receive a message within a transaction.
 
 Second, an application should always hold a lock on a conversation group before updating the state of the conversation group or the state of any message in the conversation group. When an application receives a message within a transaction, the application automatically locks the conversation group.
 
-## See also
+## Related content
 
 - [SAVE TRANSACTION (Transact-SQL)](../../t-sql/language-elements/save-transaction-transact-sql.md)
-- [Understanding Database Engine Errors](../../relational-databases/errors-events/understanding-database-engine-errors.md)
+- [Understanding Database Engine Errors](../../relational-databases/errors-events/understanding-database-engine-errors.md)

docs/database-engine/service-broker/how-to-activate-service-broker-message-delivery-in-databases-transact-sql.md

@@ -1,43 +1,45 @@
 ---
-title: "How to: Activate Service Broker Message Delivery in Databases (Transact-SQL)"
+title: "How To: Activate Service Broker Message Delivery in Databases (Transact-SQL)"
 description: "By default, Service Broker message delivery is active in a database when the database is created."
 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: how-to
 ---
 
-# How to: Activate Service Broker Message Delivery in Databases (Transact-SQL)
+# How to: Activate Service Broker message delivery in databases (Transact-SQL)
 
 [!INCLUDE [sql-asdbmi](../../includes/applies-to-version/sql-asdbmi.md)]
 
-By default, Service Broker message delivery is active in a database when the database is created. When message delivery is not active, messages remain in the transmission queue. To determine whether Service Broker is active for a database, check the **is_broker_enabled** column of the **sys.databases** catalog view.
+By default, Service Broker message delivery is active in a database when the database is created. When message delivery isn't active, messages remain in the transmission queue. To determine whether Service Broker is active for a database, check the `is_broker_enabled` column of the `sys.databases` catalog view.
 
-> [!NOTE]
-> Activating Service Broker allows messages to be delivered to the database. A Service Broker endpoint must be created to send and receive messages from outside of the instance.
+> [!NOTE]  
+> Activating Service Broker allows messages to be delivered to the database. You must create a Service Broker endpoint to send and receive messages from outside of the instance.
 
-## To activate Service Broker in a database
+## Activate Service Broker in a database
 
-- Alter the database to set the ENABLE_BROKER option.
+- Alter the database to set the `ENABLE_BROKER` option.
 
-## Example
+## Examples
 
 ```sql
-    USE master ;
-    GO
+USE master;
+GO
 
-    ALTER DATABASE AdventureWorks2008R2 SET ENABLE_BROKER ;
-    GO
+ALTER DATABASE AdventureWorks2008R2
+    SET ENABLE_BROKER;
+GO
 ```
 
 [!INCLUDE [SQL Server Service Broker AdventureWorks2008R2](../../includes/service-broker-adventureworks-2008-r2.md)]
 
-## See also
+## Related content
 
 - [How to: Deactivate Service Broker Message Delivery in Databases (Transact-SQL)](how-to-deactivate-service-broker-message-delivery-in-databases-transact-sql.md)
-- [How to: Activate Service Broker Networking (Transact-SQL)](how-to-activate-service-broker-networking-transact-sql.md)
+- [How to: Activate Service Broker networking (Transact-SQL)](how-to-activate-service-broker-networking-transact-sql.md)
 - [ALTER DATABASE (Transact-SQL)](../../t-sql/statements/alter-database-transact-sql.md)
-- [sys.databases (Transact-SQL)](../../relational-databases/system-catalog-views/sys-databases-transact-sql.md)[sys.transmission_queue (Transact-SQL)](../../relational-databases/system-catalog-views/sys-transmission-queue-transact-sql.md)
+- [sys.databases (Transact-SQL)](../../relational-databases/system-catalog-views/sys-databases-transact-sql.md)
+- [sys.transmission_queue (Transact-SQL)](../../relational-databases/system-catalog-views/sys-transmission-queue-transact-sql.md)

docs/database-engine/service-broker/how-to-activate-service-broker-message-forwarding-transact-sql.md

@@ -1,40 +1,42 @@
 ---
-title: "How to: Activate Service Broker Message Forwarding (Transact-SQL)"
+title: "How To: Activate Service Broker Message Forwarding (Transact-SQL)"
 description: "Message forwarding allows an instance of SQL Server to accept messages from outside the instance and send those messages to a different instance. Message forwarding is configured on a Service Broker endpoint."
 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: how-to
 ---
 
-# How to: Activate Service Broker Message Forwarding (Transact-SQL)
+# How to: Activate Service Broker message forwarding (Transact-SQL)
 
 [!INCLUDE [sql-asdbmi](../../includes/applies-to-version/sql-asdbmi.md)]
 
 Message forwarding allows an instance of SQL Server to accept messages from outside the instance and send those messages to a different instance. Message forwarding is configured on a Service Broker endpoint.
 
-## To activate Service Broker message forwarding
+## Activate Service Broker message forwarding
 
-1. Activate Service Broker networking if networking is not already active. For more information on Service Broker networking, see [How to: Activate Service Broker Networking (Transact-SQL)](how-to-activate-service-broker-networking-transact-sql.md).
+1. Activate Service Broker networking if networking isn't already active. For more information on Service Broker networking, see [How to: Activate Service Broker networking](how-to-activate-service-broker-networking-transact-sql.md).
 
-2. Alter the endpoint to activate message forwarding, and specify the maximum size, in megabytes, for forwarded messages.
+1. Alter the endpoint to activate message forwarding, and specify the maximum size, in megabytes, for forwarded messages.
 
-## Example
+## Examples
 
 ```sql
-    USE master ;
-    GO
-
-    ALTER ENDPOINT BrokerEndpoint
-        FOR SERVICE_BROKER ( MESSAGE_FORWARDING = ENABLED,
-                             MESSAGE_FORWARD_SIZE = 10 ) ;
-    GO
+USE master;
+GO
+
+ALTER ENDPOINT BrokerEndpoint FOR SERVICE_BROKER
+(
+    MESSAGE_FORWARDING = ENABLED,
+    MESSAGE_FORWARD_SIZE = 10
+);
+GO
 ```
 
-## See also
+## Related content
 
-- [How to: Activate Service Broker Networking (Transact-SQL)](how-to-activate-service-broker-networking-transact-sql.md)
+- [How to: Activate Service Broker networking (Transact-SQL)](how-to-activate-service-broker-networking-transact-sql.md)
 - [How to: Deactivate Service Broker Message Forwarding (Transact-SQL)](how-to-deactivate-service-broker-message-forwarding-transact-sql.md)

docs/database-engine/service-broker/how-to-activate-service-broker-networking-transact-sql.md

@@ -1,45 +1,48 @@
 ---
-title: "How to: Activate Service Broker Networking (Transact-SQL)"
-description: "Service Broker does not send or receive messages over the network by default."
+title: "How To: Activate Service Broker Networking (Transact-SQL)"
+description: Learn how to activate Service Broker networking in an instance by creating an endpoint for Service Broker.
 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: how-to
 ---
 
-# How to: Activate Service Broker Networking (Transact-SQL)
+# How to: Activate Service Broker networking (Transact-SQL)
 
 [!INCLUDE [sql-asdbmi](../../includes/applies-to-version/sql-asdbmi.md)]
 
-Service Broker does not send or receive messages over the network by default. To activate Service Broker networking in an instance, create an endpoint for Service Broker.
+Service Broker doesn't send or receive messages over the network by default. To activate Service Broker networking in an instance, create an endpoint for Service Broker.
 
-> [!NOTE]
-> Creating a Service Broker endpoint causes SQL Server to accept TCP/IP connections on the port specified. Service Broker transport security allows you to require authorization for connections to the port. If the computer that runs SQL Server has a firewall enabled, the firewall configuration on that computer must allow both incoming connections for the port specified in the endpoint. For more information on Service Broker transport security, see [Service Broker Transport Security](service-broker-transport-security.md).
+Creating a Service Broker endpoint causes SQL Server to accept TCP/IP connections on the port specified. Service Broker transport security allows you to require authorization for connections to the port. If the computer that runs SQL Server has a firewall enabled, the firewall configuration on that computer must allow both incoming connections for the port specified in the endpoint. For more information on Service Broker transport security, see [Service Broker Transport Security](service-broker-transport-security.md).
 
-### To activate Service Broker networking
+## Activate Service Broker networking
 
-- Create a Service Broker endpoint, specifying the port number and the authentication level.
+Create a Service Broker endpoint, specifying the port number and the authentication level.
 
-## Example
+## Examples
 
 ```sql
-    USE master;
-    GO
-
-    CREATE ENDPOINT BrokerEndpoint
-        STATE = STARTED
-        AS TCP ( LISTENER_PORT = 4037 )
-        FOR SERVICE_BROKER ( AUTHENTICATION = WINDOWS ) ;
-    GO
+USE master;
+GO
+
+CREATE ENDPOINT BrokerEndpoint
+    STATE = STARTED
+    AS TCP (
+        LISTENER_PORT = 4037
+    )
+    FOR SERVICE_BROKER (
+        AUTHENTICATION = WINDOWS
+    );
+GO
 ```
 
-## See also
+## Related content
 
-- [How to: Pause Service Broker Networking (Transact-SQL)](how-to-pause-service-broker-networking-transact-sql.md)
-- [How to: Resume Service Broker Networking (Transact-SQL)](how-to-resume-service-broker-networking-transact-sql.md)
+- [How to: Pause Service Broker networking (Transact-SQL)](how-to-pause-service-broker-networking-transact-sql.md)
+- [How to: Resume Service Broker networking (Transact-SQL)](how-to-resume-service-broker-networking-transact-sql.md)
 - [How to: Deactivate Service Broker Networking (Transact-SQL)](how-to-deactivate-service-broker-networking-transact-sql.md)
 - [ALTER DATABASE (Transact-SQL)](../../t-sql/statements/alter-database-transact-sql.md)
 - [CREATE ENDPOINT (Transact-SQL)](../../t-sql/statements/create-endpoint-transact-sql.md)