SQL Server Queues Retaining Values After Restart

[Skittle]

I have a need to set up an asynchronous process using queues. The SQl Server queues looks like it will do the job but I have three queries about them.

1) If SQL server 2008 is restarted and there are entries on a queue, do they get lost or are they retained?

2) Most examples I have found show two queues. One for a sender and one for a receiver with a contract in between. I could add entries to the one queue and then take them from the same queue without the need to send them to a second queue. Why do I need to use two when both the send and receive applications ( although seperate ) are on the same server? Could a transaction perhpas lock the queue when writing or reading?

3) Are there any advantages of using MSMQ queues instead of sql server queues?





Dazed and confused.

Remember.. 'Depression is just anger without enthusiasum'.

 

[yelworcm]

1) The queues should retain any value, until they are RECEIVEd by some process. Only RECEIVE will delete something from a queue.

2) Error messages (invalid message, etc.) are sent back to the originating queue.

3) I have never used MSMQ, but I suspect they use a lot of the same code. You may get some more flexibility through MSMQ.

 

[Skittle]

Ok Thanks.

Dazed and confused.

Remember.. 'Depression is just anger without enthusiasum'.