Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

ServiceQueue Class

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)

[TypeConverterAttribute(typeof(LocalizableTypeConverter))]
[PhysicalFacetAttribute]
[EvaluationModeAttribute(AutomatedPolicyEvaluationMode.CheckOnSchedule)]
[LocalizedPropertyResourcesAttribute("Microsoft.SqlServer.Management.Smo.Broker.BrokerLocalizableResources", 
	true)]
public sealed class ServiceQueue : ScriptSchemaObjectBase, 
	IObjectPermission, IExtendedProperties, ICreatable, IAlterable, IDroppable, 
	IScriptable

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

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.

Thread Safety

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

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

Community Additions

ADD
Show:
© 2015 Microsoft