Post reply

Question about MAX_QUEUE_READERS in Service Broker.

  • May 1, 2013 at 2:52 pm

    #277068

    Guys,

    I have a Question about MAX_QUEUE_READERS option in Service Broker.

    In a high transaction environment where inserts/updates/deletes are very high, would it be affected by

    having MAX_QUEUE_READERS value higher than 1 ?

    What happens when a INSERT statement is issued and then Immediately DELETE is issued for the same record

    and because of MAX_QUEUE_READERS being 2 or 3 ...DELETE gets processed before INSERT (Parallel Processing) ?

    OR I am not correct with my understanding of MAX_QUEUE_READERS ?

    I have a Production Issue where sometimes Queue backs up because of high User Activity and we have MAX_QUEUE_READERS set as 1.

    I am thinking of increasing it to may be 5, but would like to know ,that we don't end up with Orphan Records due

    to multi-threaded parallel process created by MAX_QUEUE_READERS.

    Thanks.

  • May 1, 2013 at 2:54 pm

    #1611727

    duplicate post.

    There's no need to post the same question in multiple forums.

    The Recent Topics function most people use shows us your post immediately.

    crossposting will wastes people's time and fragments replies.

    No replies to this thread please. Direct replies to http://www.sqlservercentral.com/Forums/Topic1448609-1281-1.aspx

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • May 1, 2013 at 9:17 pm

    #1611772

    Do you know the answer though ?

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply