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     Run time for calling SQL proc

Read-Only Read-Only Topic
Go
Search
Notify
Tools
Run time for calling SQL proc
 Login/Join
 
k.lane
Platinum Member
posted
Hi,

One of the developers at my location contacted me this morning regarding a report that uses a call to a SQL proc to extract an answer set. The problem is that it takes about 12 1/2 minutes for the answer set to return.

He has about 15 other reports that use the same method. All these other reports work fine. If you run this particular proc in analyzer, it comes back in seconds.

Here's the specifics:

SQL SQLMSS SET SERVER servername
SQL SQLMSS
EX DRESFCST.dbo.proc_name &RPTING_SET, '&RPT_LVL';
TABLE FILE SQLOUT
PRINT *
ON TABLE HOLD AS RPTDATA
END

All required columns in the base tables used in the procs have been indexed.

The sql calls are coded exactly the same as they are in the other 15 reports.

Any ideas?
 
Posts: 177 | Location: Calgary, Alberta, Canada | Registered: April 25, 2005Report This Post
Lenny Ward
Platinum Member
posted Hide Post
When we have had a problem like that in the past we use SQL Profiler to look at the query plan and usually end up re-compiling the sql proc.
 
Posts: 104 | Location: Boston | Registered: April 23, 2003Report This Post
k.lane
Platinum Member
posted Hide Post
But, the problem does not appear to be the proc in this case. The proc runs very quickly, as do the others.
 
Posts: 177 | Location: Calgary, Alberta, Canada | Registered: April 25, 2005Report This Post
j.gross
Virtuoso
posted Hide Post
An obvious question: Did you test the proc directly with the particular parameter values (of &RPTING_SET, &RPT_LVL) that occasioned the problem?
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
k.lane
Platinum Member
posted Hide Post
Yes we did.

The developer may end up writing the report in WebFOCUS instead now to get around the problem even though this is more of a bandaid solution that trying to get to the root cause.
 
Posts: 177 | Location: Calgary, Alberta, Canada | Registered: April 25, 2005Report This Post
Lenny Ward
Platinum Member
posted Hide Post
Have you tried running SQL Profiler while the proc was being executed from WebFOCUS?
 
Posts: 104 | Location: Boston | Registered: April 23, 2003Report 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     Run time for calling SQL proc

Copyright © 1996-2020 Information Builders