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.
Does anyone know where to locate any commands that would help optimize the way webFOCUS generates the SQL that is passed to DB2?
When I run these commands :
SET TRACEOFF=ALL
SET TRACEUSER = ON
SET TRACEON = STMTRACE//CLIENT
SET TRACEON = SQLAGGR//CLIENT
SET TRACESTAMP=OFF
SET XRETRIEVAL=OFF
I often find webFOCUS sending using subselects when not necessary, not translating IN statements properly, among other things. Also I'd like to have the group by statements done on the FOCUS side of things instead of the DB2 side of things.
Also I know that IB changed the way that sql was generated between versions 7.1.4 and 7.6.7. Is there maybe a command that I can use that will utilize the old translations? (which appears to be more efficient in some cases) over the new translationsThis message has been edited. Last edited by: Kerry,
Eric Woerle WF 7.6.7 Reportting Server ETL 7.6.10 Dev Studio 7.6.7
Also I'd like to have the group by statements done on the FOCUS side of things instead of the DB2 side of things.
I'm not sure why you want to do this. It is more efficient for the relational engine to do this.
But where I would have you look would be on the IBI site for anything related to relational efficiencies, Data Administration manuals, sql translator, etc.
Your branch may be able to provide some presentations on relational efficiencies as relates to joins, aggregation, and selection. If you can't find any, private post to me with your email address and I'd be happy to forward what I have.
I know it seems strange to want to do my group by's on the reporting server, but our reporting system is much faster then our DB2 system (due to not having to share with other company resources). Also our users are running into resource limit issues. So if we can get the SQL more efficient and do less work in DB2, then we should be able to speed up the queries of our users while utilizing the excess resources we have at our reporting server.
Eric Woerle WF 7.6.7 Reportting Server ETL 7.6.10 Dev Studio 7.6.7
Then don't put the sort statements in the original request, just the WHERE statements. Hold the data when you get it back and do what you want to with it. Or do the BY's with a PRINT not a SUM, which ever gets you what you want.
This is the first time I've heard that the DB2 server is slower than the reporting server, though this has given me something to think about in our environment.