Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Using Activity Monitor, I am consistently seeing the following query showing an average duration of over 300 seconds:

WAITFOR(RECEIVE conversation_handle, service_contract_name, message_type_name, message_body 
                FROM ExternalMailQueue INTO @msgs), TIMEOUT @rec_timeout

There don't seem to be any adverse effects on the server, and this query is showing zeros for all other columns.

Is this normal or a cause for concern?

share|improve this question
Were you ever able to solve this issue? I am facing the same issue in my environment and working on it so please let me know what steps you finally took to solve this. – LogicInside Apr 11 '12 at 15:13
@AnkitShah apparently according to the checkmark below he implemented Mark's answer. – jcolebrand Apr 11 '12 at 15:43
up vote 1 down vote accepted

This is a Service Broker process listening to a queue for messages. 300 seconds will be the time out specified in @rec_timeout. See RECEIVE reference in books online.

share|improve this answer
Correct. Just to add: ExternalMailQueue is the Database Mail notifications queue that signals the mail processor that it has work to do. – Remus Rusanu Mar 3 '12 at 1:43

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.