Share via

ServiceRoute Class

  • Article

The ServiceRoute object represents a Service Broker route that contains the location information for the service and the database on which it is defined.

Namespace: Microsoft.SqlServer.Management.Smo.Broker
Assembly: Microsoft.SqlServer.Smo (in microsoft.sqlserver.smo.dll)

Syntax

'Declaration
Public NotInheritable Class ServiceRoute
    Inherits BrokerObjectBase
    Implements IObjectPermission, IExtendedProperties, ICreatable, IAlterable, _
    IDroppable

public sealed class ServiceRoute : BrokerObjectBase, IObjectPermission, IExtendedProperties, ICreatable, 
    IAlterable, IDroppable

public ref class ServiceRoute sealed : public BrokerObjectBase, IObjectPermission, IExtendedProperties, ICreatable, 
    IAlterable, IDroppable

public final class ServiceRoute extends BrokerObjectBase implements IObjectPermission, IExtendedProperties, 
    ICreatable, IAlterable, IDroppable

public final class ServiceRoute extends BrokerObjectBase implements IObjectPermission, IExtendedProperties, 
    ICreatable, IAlterable, IDroppable

Remarks

A route is required for message delivery. By default, each database contains a route that specifies the location as the current instance of Microsoft SQL Server.

This namespace, class, or member is supported only in version 2.0 of the Microsoft .NET Framework.

To get ServiceRoute object properties, users can be a member of the public fixed server role.

To set ServiceRoute object properties, users must be a member of the db_ddladmin or db_owner fixed database roles, or be a member of the sysadmin fixed server role. The user also requires REFERENCES permission on the specified schema.

To create a service route, users must be a member of the db_ddladmin or db_owner fixed database roles, or be a member of the sysadmin fixed server role. The user also requires REFERENCES permission on the specified schema.

To drop a service route, users must be a member of the db_ddladmin or db_owner fixed database roles, or be a member of the sysadmin fixed server role. The user also requires REFERENCES permission on the specified schema.

To grant, deny, or revoke permissions on the message type to other users, users must have CONTROL permission on the service route.

Inheritance Hierarchy

System.Object
   Microsoft.SqlServer.Management.Smo.SmoObjectBase
     Microsoft.SqlServer.Management.Smo.SqlSmoObject
       Microsoft.SqlServer.Management.Smo.NamedSmoObject
         Microsoft.SqlServer.Management.Smo.ScriptNameObjectBase
           Microsoft.SqlServer.Management.Smo.Broker.BrokerObjectBase
            Microsoft.SqlServer.Management.Smo.Broker.ServiceRoute

Example

Readme_ServiceBrokerConfiguration

Thread Safety

Any public static (Shared in Microsoft Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Platforms

Development Platforms

For a list of the supported platforms, see Hardware and Software Requirements for Installing SQL Server 2005.

Target Platforms

For a list of the supported platforms, see Hardware and Software Requirements for Installing SQL Server 2005.

See Also

Reference

ServiceRoute Members
Microsoft.SqlServer.Management.Smo.Broker Namespace

Other Resources

Service Broker Programming
Managing Service Broker
Introducing Service Broker
CREATE ROUTE (Transact-SQL)