Share via

ServiceQueue Class

  • Article

The ServiceQueue object represents a queue that stores messages and after they are received.

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

Syntax

'Declaration
Public NotInheritable Class ServiceQueue
    Inherits ScriptSchemaObjectBase
    Implements IObjectPermission, IExtendedProperties, ICreatable, IAlterable, _
    IDroppable, IScriptable

public sealed class ServiceQueue : ScriptSchemaObjectBase, IObjectPermission, IExtendedProperties, ICreatable, 
    IAlterable, IDroppable, IScriptable

public ref class ServiceQueue sealed : public ScriptSchemaObjectBase, IObjectPermission, IExtendedProperties, ICreatable, 
    IAlterable, IDroppable, IScriptable

public final class ServiceQueue extends ScriptSchemaObjectBase implements IObjectPermission, IExtendedProperties, 
    ICreatable, IAlterable, IDroppable, IScriptable

public final class ServiceQueue extends ScriptSchemaObjectBase implements IObjectPermission, IExtendedProperties, 
    ICreatable, IAlterable, IDroppable, IScriptable

Remarks

The ServiceQueue object provides asynchronous communication between services, as well as other benefits, such as automatically locking messages in the same conversation group.

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

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

To set ServiceQueue 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 queue, 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 queue, 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 receive a message, users must have RECEIVE permission on the service queue.

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

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.ScriptSchemaObjectBase
            Microsoft.SqlServer.Management.Smo.Broker.ServiceQueue

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

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

Other Resources

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