I'm struggling with a join that performs awfully slow.

I have a table file that uses an inner join...unique to another table. If performed on our production server or directly on the "WebFOCUS enviroment" it returns within 3s with 12 records. I can see it only pulling in those 12 records in the agents view in the diagnostics screen in the webconsole. So far so good.

However, if I execute the same query on my local development environment it takes minutes! It's pulling in 10's of thousands of records, at a rate of about 100/s.

If I remove the join, the query performs similar to executing it directly on the data-server (within 3s), like how I outlined in the good case. In this case also, it only pulls in 12 records instead of 50k or so.

I've been trying to hunt this down for a while already. I checked that the master-files are the same ones as used on the production environment and I saw from the agent statistics that it's really using the right table (or logical file, rather). So I think it's safe to assume the master-files aren't the problem.

What could be causing this difference in behaviour between both environments? What's causing WebFOCUS to pull in an entire table (that's what it looks like) instead of querying it properly? Any pointers to what I can look into?

This message has been edited. Last edited by: Kerry,

Switch on tracing for this requeswt. It will tell you exactly what is being done sql-wise and this may shed some light on the difference in behaviour.

What is the source of the two joined tables.

If WebFOCUS thinks they are from separate sources, then it will potentially retrieve all records from both, then join locally.

From the same source... they should be, but maybe one of the masters is from a different location and pointing to the data-server via my dev-environment. That's something to look into, thanks!