use a queue when you want a publish-subscribe model. (asynchronous) if you try to code a mechanism for multiple processes to pluck messages off a heap organized table, ensuring that no more than one process picks up each message, you are recreating what a queue automatically does for you. there are other use cases as well for automatic notification/invocation of pl/sql upon arrival of a message in an asynchronous way that make queues indispensable. who told you that you needed a queue? Job --- On Wed, 8/25/10, Joe Smith <joe_dba@xxxxxxxxxxx> wrote: From: Joe Smith <joe_dba@xxxxxxxxxxx> Subject: Queues To: oracle-l@xxxxxxxxxxxxx Date: Wednesday, August 25, 2010, 11:33 AM I have been reading the PDFs and documents on MOS, but can someone tell me the difference or advantage of using Queues instead of writing messages to a regular heap-organized Oracle table? Or what is the real advantage of queues that I am missing?