Broker:Remote Message Ack Event Class

SQL Server generates a Broker:Remote Message Ack event when Service Broker sends or receives a message acknowledgement.

Broker:Remote Message Ack Event Class Data Columns

Data column Type Description Column number Filterable

ApplicationName

nvarchar

The name of the client application that created the connection to an instance of SQL Server. This column is populated with the values passed by the application rather than the displayed name of the program.

10

Yes

BigintData1

bigint

The sequence number of the message that contains the acknowledgement.

52

No

BigintData2

bigint

The sequence number of the message being acknowledged.

53

No

ClientProcessID

int

The ID assigned by the host computer to the process where the client application is running. This data column is populated if the client process ID is provided by the client.

9

Yes

DatabaseID

int

The ID of the database specified by the USE database statement, or the ID of the default database if no USE databasestatement has been issued for a given instance. SQL Server Profiler displays the name of the database if the Server Name data column is captured in the trace and the server is available. Determine the value for a database by using the DB_ID function.

3

Yes

EventClass

int

The type of event class captured. Always 149 for Broker:Message Ack.

27

No

EventSequence

int

Sequence number for this event.

51

No

EventSubClass

nvarchar

The type of event subclass, providing further information about each event class. This column may contain the following values.

  • Message With Acknowledgement Sent
    Service Broker sent an acknowledgement as part of a normal sequenced message.
  • Acknowledgement Sent
  • Service Broker sent an acknowledgement outside of a normal sequenced message.
  • Message With Acknowledgement Received
    Service Broker received an acknowledgement as part of a normal sequenced message.
  • Acknowledgement Received
    Service Broker received an acknowledgement outside of a sequenced message.

21

Yes

GUID

uniqueidentifier

The conversation ID of the dialog. This identifier is transmitted as part of the message, and is shared between both sides of the conversation.

54

No

HostName

nvarchar

The name of the computer on which the client is running. This data column is populated if the host name is provided by the client. To determine the host name, use the HOST_NAME function.

8

Yes

IntegerData

int

The fragment number of the message that contains the acknowledgement.

25

No

IntegerData2

int

The fragment number of the message being acknowledged.

55

No

IsSystem

int

Indicates whether the event occurred on a system process or a user process.

0 = user

1 = system

60

No

LoginSid

image

The security identification number (SID) of the logged-in user. Each SID is unique for each login in the server.

41

Yes

NTDomainName

nvarchar

The Windows domain to which the user belongs.

7

Yes

NTUserName

nvarchar

The name of the user that owns the connection that generated this event.

6

Yes

RoleName

nvarchar

The role of the instance that is acknowledging the message. This is either initiator or target.

38

No

ServerName

nvarchar

The name of the instance of SQL Server being traced.

26

No

SPID

int

The server process ID assigned by SQL Server to the process associated with the client.

12

Yes

StartTime

datetime

The time at which the event started, when available.

14

Yes

TransactionID

bigint

The system-assigned ID of the transaction.

4

No

See Also

Other Resources

Introducing Service Broker
Dialog Conversations

Help and Information

Getting SQL Server 2005 Assistance