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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SHARING] Optimization - ENGINE SQLMSS SET CURSORS [CLIENT|SERVER], and beyond.

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SHARING] Optimization - ENGINE SQLMSS SET CURSORS [CLIENT|SERVER], and beyond.
 Login/Join
 
Guru
posted
We've recently changed edasprof to use client cursors rather than running them on the server side and have seen improvements across the board (sometimes from several minutes to just a few seconds). There is documentation on this setting here.

I was wondering if anyone else has done this as well and if they have run into any issues with this. We mostly use a single connection/adapter and don't typically report from multiple instances. Also, do you guys know of any other settings that can help (like is there a setting to increase the RAM for agents?).

Thanks a lot,
-J

EDIT: I guess another old post on this topic that nobody has responded to can be found here.

This message has been edited. Last edited by: J,


WebFOCUS 7.7.03/8.0.08
Dev Studio 7.7.03/8.0.08
App Studio 8.0.08
Windows 7
ALL Outputs
 
Posts: 402 | Location: Upland, IN | Registered: June 08, 2012Report This Post
Gold member
posted Hide Post
Hi J,

If it's set for CLIENT does it queue reports from multiple instances?

Also, have you tried messing around with SERVER and FETCHSIZE as 100 as suggested in the documentation?

I'm going to try this as soon as I have some spare time.


WebFOCUS App Studio 8103
Windows7
All outputs
 
Posts: 58 | Location: London, UK | Registered: May 09, 2011Report This Post
Guru
posted Hide Post
The CLIENT setting does only read one answer set from the same instance. However, we rarely run into this problem. The few times we do we can override the setting back to SERVER (or blank). I have tried working with FETCHSIZE (it is set to 100 by default I think). If I increase it to 5000 it only improves runtime by a few seconds max.

Word of Warning, If you are using a bunch complicated match statements or other techniques that require multiple instances the report will break and you will need to override the setting for those specific reports.

Multiple table file (and hold) statements work fine as do sql passthru statements.

This message has been edited. Last edited by: J,


WebFOCUS 7.7.03/8.0.08
Dev Studio 7.7.03/8.0.08
App Studio 8.0.08
Windows 7
ALL Outputs
 
Posts: 402 | Location: Upland, IN | Registered: June 08, 2012Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SHARING] Optimization - ENGINE SQLMSS SET CURSORS [CLIENT|SERVER], and beyond.

Copyright © 1996-2020 Information Builders