Focal Point Banner


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.



Read-Only Read-Only Topic
Go
Search
Notify
Tools
Joins vs. Match
 Login/Join
 
Stan
Gold member
posted
I've been given conflicting information and wanted to verify what the group says. In terms of pure efficiency, what is the difference between a Join and using Match to get the same results?

Thanks in advance.

Stan
 
Posts: 90 | Registered: April 15, 2004Report This Post
NathanC
Member
posted Hide Post
If you do a Join and you are using a RDBMS internally the whole request is passed to the remote database engine and would be quicker. Match has to create a HOLD file and you have to create a report in a further step.
 
Posts: 16 | Location: New York | Registered: August 25, 2006Report This Post
Leah
Virtuoso
posted Hide Post
Join vs Match. I have my issues, depends what you want to do. As NathanC indicated part of it is where you want the work to occur at the database or within FOCUS/WebFOCUS. It also depends on what you want to do. Join to me is best for selection where the selection is pretty straight forward. Match (which honestly I avoid when I can) is good when you have populations you are trying to identify and screen out certain things. Which is more efficient? I'd go with join most of the time, but as indicated you can't always get what you want with a join.


Leah
 
Posts: 1317 | Location: Council Bluffs, IA | Registered: May 24, 2004Report This Post
hammo1j
Master
posted Hide Post
It's Horses for Courses on this one: Match is a more suitable tool for many operations than Join and vice versa.

I am looking forward to the day that SQL gets its own version of the MATCH command, since SQL is gradually evolving into WebFOCUS!


Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2
Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
 
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic


Copyright © 1996-2020 Information Builders