Skip to content

managing-service-broker.md

Latest commit

 

History

History
41 lines (27 loc) · 3.76 KB

managing-service-broker.md

File metadata and controls

41 lines (27 loc) · 3.76 KB
title Managing Service Broker
description Managing Service Broker
author markingmyname
ms.author maghan
ms.date 05/24/2019
ms.service sql
ms.topic reference
helpviewer_keywords
Service Broker [SMO]
monikerRange =azure-sqldw-latest||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current

Managing Service Broker

[!INCLUDEsql-asdbmi]

In SMO, the [!INCLUDEssSB] objects are found in the Microsoft.SqlServer.Management.Smo.Broker namespace, which requires a reference to the Microsoft.SqlServer.Smo.dll. A reference to the Microsoft.SqlServer.ServiceBrokerEnum.dll is also required for supporting class information.

SMO provides a set of [!INCLUDEssSB] objects that permit programmatic management (DDL) of the [!INCLUDEssSB] implementation. This includes defining the message types, contracts, queues, and services. Because SMO is a management tool that is not intended for data manipulation, sending and receiving [!INCLUDEssSB] messages is not supported by SMO.

In SMO, the xref:Microsoft.SqlServer.Management.Smo.Database.ServiceBroker%2A object is the top-level class under which all the [!INCLUDEssSB] functionality resides. A [!INCLUDEssSB] implementation is required for each database that is participating in the distributed messaging application. Therefore, the xref:Microsoft.SqlServer.Management.Smo.Broker.ServiceBroker object is a child of the xref:Microsoft.SqlServer.Management.Smo.Database object.

The xref:Microsoft.SqlServer.Management.Smo.Broker.ServiceBroker object contains collections of the following objects that are used to define the [!INCLUDEssSB] implementation:

  • xref:Microsoft.SqlServer.Management.Smo.Broker.MessageType objects represent message types that define the content of messages.

  • xref:Microsoft.SqlServer.Management.Smo.Broker.MessageTypeMapping objects represent contracts that specify the direction and type of messages in a given conversation.

  • xref:Microsoft.SqlServer.Management.Smo.Broker.ServiceQueue objects store messages prior to sending and after they are received. They provide asynchronous communication between services, as well as other benefits, such as automatically locking messages in the same conversation group.

  • xref:Microsoft.SqlServer.Management.Smo.Broker.BrokerService objects represent [!INCLUDEssSB] services, which are the addressable endpoints for conversations. [!INCLUDEssSB] messages are sent from one service to another service. A service specifies a queue to hold messages, and specifies the contracts for which the service can be the target.

  • xref:Microsoft.SqlServer.Management.Smo.Broker.RemoteServiceBinding objects represent the settings that [!INCLUDEssSB] uses for security and authentication when communicating with a remote service.

  • xref:Microsoft.SqlServer.Management.Smo.Broker.ServiceRoute objects represents a [!INCLUDEssSB] route, which contains the location information for the service and the database on which it is defined. A route is required for message delivery. By default, each database contains a route that specifies the location as the current instance of [!INCLUDEssNoVersion].

See Also

xref:Microsoft.SqlServer.Management.Smo.Broker
SQL Server Service Broker