Joe,
I would tend to agree that both data queues and result sets have their place.
One
thing I have found with data queues is that both of these impose a lot of
overhead.
I took an application we had and converted from a result set to get around some
limitations to a data queue. The performance got worse, but it got around the
problem.
Next, I converted that same application to use http tunneling and the
performance
improvement was very noticeable. Since then, I know that data queues have been
worked on. Do you know if the performance problems have been fixed? I have a
project coming up I would like to use data queues on, but I am a apprehensive.
David Morris
>>> joepluta@PlutaBrothers.com 08/30/01 04:08PM >>>
...No, I think you're trying to defend stored procedures vs. data queues. Me,
I admit that stored procedures may be very good for simple queries and even
simple updates, but that data queues are much better for more sophisticated
transaction requirements. I've stated why. I'd be interested to see your
response.,,,
