As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
Originally posted by Kamesh: Both the tables are in the same database.
Are the database CONNECTION strings in the access (.acx) files the same? If you look at the master (.mas) files, do both have keys on the fields you are joining on?
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
When we join two tables with "ALL" option, why it is executing the sql (on background) for every record comparison
Define 'it' please. Do you see WebFOCUS issuing 10 requests (do you see 10 times the same sql being issued to the sql engine)? Or is the sql engine executing the single request from webfocus 10 times over? iaw: show us the sql that is being generated.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
Originally posted by J: Remind me if I am incorrect, but doesn't each field need to be checked to every other field with a join all?
That means in a 10x10 table, 100 comparisons are being made. I'm guessing it is executing for each record (1->10 for one execution).
Do you really want all the records joined to all the other records or am I thinking of the wrong "all"?
Thats the way that I'm understanding it too J,
e.g table 1 a b c
table 2
c d e
joined table
a c b c c c a d b d c b c c c d c e
So it will calculate all of these joins then apply your where clause Kamesh,
Personally if I was to join based on a couple of where clauses I would use a left outer join as it will do the join based on a where clause thus reducing the number of transactions it has to compute.
Plus I would break down the tab.a first so there are less lines to check
i.e.
select * from tab b left outer join (Select * from tab a where a.key1=0002 ) ta on (b.col1 = ta.col1)
When we join two tables with "ALL" option, why it is executing the sql (on background) for every record comparison.
ONCE AGAIN: I has nothing to do with the "ALL". Any time you join a HOLD file to a Database Server table, and report against that Join structure, that is what happens.
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005