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.
What is the source of your data? SQL Server, Oracle, et cetera.
Do you have joins in the business view? If so, run a request you consider inefficient with SQL Traces on to see how your joins are being generated.
Are you joining different data types? With or without a Business View, if you join two different database tables (eg. sequential to Oracle) you'll end up causing table scans that aren't very efficient.
Business Views don't necessarily give you faster access. They just encapsulate the Joins, Filters and organize your data in folders so report developers don't have to keep recreating them.
I would start with the SQL Trace.
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015
While WebFOCUS allows you to create DEFINE based joins, there are some considerations. Specifically, if the defined field can't be translated into the same SQL statement, then you are effectively turning optimization off and potentially creating multiple SELECTS and asking WebFOCUS to join the answer sets. So, you have to look at the joins that use a virtual field and decide if there's a better way to create the join.