TechNet
Export (0) Print
Expand All

Broker:Message Drop Event Class

 

SQL Server generates a Broker:Message Drop event when Service Broker is unable to retain a received message that should have been delivered to a service in this instance. For messages that should have been forwarded, see Broker:Forwarded Message Dropped Event Class.

Data columnTypeDescriptionColumn numberFilterable
Application NamenvarcharThe 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.10Yes
BigintData1bigintThe sequence number of the dropped message.52No
BigintData2bigintThe sequence number of the last message successfully acknowledged.53No
ClientProcessIDintThe 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.9Yes
DatabaseIDintThe ID of the database specified by the USE database statement, or the ID of the default database if no USE database statement has been issued for a given instance. SQL Server Profiler displays the name of the database if the ServerName data column is captured in the trace and the server is available. Determine the value for a database by using the DB_ID function.3Yes
ErrorintThe message id number in sys.messages for the text in the event.31No
EventClassintThe type of event class captured. Always 160 for Broker:MessageDrop.27No
EventSequenceintSequence number for this event.51No
EventSubClassnvarcharIndicates whether the dropped message was a sequenced message. One of two values:

 Sequenced Message. The dropped message was a sequenced message.

 Unsequenced Message. The dropped message was not a sequenced message.
21Yes
GUIDuniqueidentifierThe conversation ID of the conversation that the dropped message belongs to. This identifier is transmitted as part of the message, and is shared between both sides of the conversation.54No
HostNamenvarcharThe 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.8Yes
IntegerDataintThe fragment number of the dropped message.25No
IntegerData2intThe message fragment number that the dropped message was acknowledging.55No
IsSystemintIndicates whether the event occurred on a system process or a user process. 1 = system, 0 = user.60No
LoginNamenvarcharThe name of the login of the user (either SQL Server security login or the Windows login credentials in the form of DOMAIN\Username).11No
LoginSidimageThe security identification number (SID) of the logged-in user. Each SID is unique for each login in the server.41Yes
NTDomainNamenvarcharThe Windows domain to which the user belongs.7Yes
NTUserNamenvarcharThe name of the user that owns the connection that generated this event.6Yes
ObjectNamenvarcharThe conversation handle of the dialog.34No
RoleNamenvarcharThe role of the conversation handle. This is either initiator or target.38No
ServerNamenvarcharThe name of the instance of SQL Server being traced.26No
SeverityintSeverity number for the text in the event.29No
SPIDintThe server process ID assigned by SQL Server to the process associated with the client.12Yes
StartTimedatetimeThe time at which the event started, when available.14Yes
StateintIndicates the location within the SQL Server source code that produced the event. Each location that may produce this event has a different state code. A Microsoft support engineer can use this state code to find where the event was produced..30No
TextDatantextThe reason that SQL Server dropped the message.1Yes
TransactionIDbigintThe system-assigned ID of the transaction.4No

SQL Server Service Broker

Show:
© 2016 Microsoft