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 email@example.com for further assistance. Reference the community FAQ to learn more about the community.
We have both Oracle and SQL Server. I've been testing access to both and found the settings below have greatly improved retrieval.
-* Oracle optimization settings ENGINE SQLORA SET FETCHSIZE 5000 ENGINE SQLORA SET OPTIMIZATION ON
-* SQL Server optimization settings ENGINE SQLMSS SET CURSORS CLIENT ENGINE SQLMSS SET FETCHSIZE 5000 ENGINE SQLMSS SET OPTIMIZATION ON
I'm wondering why IBI doesn't include these settings in their native adapters since, I believe, they are valid for any query or is there a drawback to automatically using these settings?
Do others have experiences they would like to share to improve performance? I tried various values for the fetchsize option reading 3M rows and creating a hold file with PRINT * just to exercise it and found the FETCHSIZE of 1000, 2000, 3000, 4000, and 5000 only varied by about 5 seconds. Thanks.This message has been edited. Last edited by: BobSh,
WebFOCUS 7.7.05M, gen 144, Windows 2008 Server R2 64-bit, Tomcat 6.0.33, IIS 7.0, SQL Server, Excel 2013, PDF, HTML, FOCUS files.
Posts: 88 | Location: Seattle | Registered: March 29, 2007