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.
The best piece of advice is to utilise the RDBMS' facilities whenever you can. I'm sorry to say that FOCUS (the original and genuine) has always been less than equal to the capabilities of the remote RDBMS when it comes to sorting.
As you have obviously already been informed, use the SQL passthru ability within WebFOCUS to get the RDBMS to do as much of the work as possible. That includes summation, ordering, predicates and especially JOINs etc. If you are not able to use the passthru then get your DBAs to create efficient views of your data instead. Try and return the minimum amount of records to WebFOCUS and then utilise WF for what it does better than the rest - report formatting.
T
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
One of the things that I do to speed up WebFocus reporting against SQL tables is to use TABLEF to retrieve the data, including any WHERE statements that SQL can understand to bring back fewer rows and eliminate any DEFINEs, EDIT's and anything that may turn optimization off. Keep the request simple, put the data in a hold file, then do all your fancy formating, defines, calculations, etc. against the HOLD file. If the fields your sorting BY are indexed on the SQL table, then use TABLE and let SQL do the sorting for you. It's very helpful to look at the trace and see the SQL is being generated.
Good Luck, Carol
WebFOCUS 7.6.6/TomCat/Win2k3
Posts: 428 | Location: Springfield, MA | Registered: May 07, 2003