RE: AQ Vs Streams

Thanks, All.

Here is the design we are trying to implement.

Source Application enqueues the message to the source queue. Source queue should let the destination application know that there are some data waiting for it and the destination application should come & dequeue the data. The destination application is not allowed to keep polling the source queue. Its a kind of triggering mechanism to the queue which should alert the subscribers that there are some new data. Any recommendations how to implement this?

Thanks,
Raja.

-----Original Message-----
From: McCartney, Bruce [mailto:bruce.mccartney_at_dbinfosystems.com] Sent: Tuesday, January 03, 2006 7:51 PM
To: Nagarajan.Subbiah_at_aetn.com; ORACLE-L Subject: RE: AQ Vs Streams

Raja,
AQ is a lower level feature for generic message processing based on user-defined events. Streams uses AQ to enable replication events to be queued. The Streams API sits on top of both AQ and LOGMINER and facilitates high-level definition and management of event-based replication. Hope that helps...

Bruce  

> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Subbiah, Nagarajan
> Sent: January 3, 2006 5:45 PM
> To: ORACLE-L
> Subject: AQ Vs Streams
>
> Hi List,
>
> We are using oracle 9.2.0.5 on HP-UX. Some of our developers
> are planning to use the Advanced Queueing. When I look at the
> Oracle Streams documentation, it is almost similar to the
> Advanced Queueing. What is the difference between the Streams
> and Advanced Queueing? What would be the ideal solution if we
> plan to migrate to Oracle 10G down the line.
>
> Thanks in Advance.
>
> -Raja
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
http://www.freelists.org/webpage/oracle-l