Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


Tip of the Day
Language: SQL
Expertise: Beginner
Apr 1, 1997

OPO Performance

Question:
I am having a hard time getting my OPO application to show decent performance. It's running on a 32MB Win3.1 PC, and queries a Solaris x86 Oracle Server using TCP/IP as the network protocol. When I perform a query using the supplied query buttons, the query comes back fairly quick. But then when I want to issue a new query of the whole database, I click on the re-query button (the one that brings all the records back, so you're not just further refining the first query, but querying the whole database). This time it takes forever to get the whole database back in order to perform a new query on the whole database.

Maybe my methodology is faulty. I'd love some guidance, because I'm ready to throw in the towel and forget about OPO.

Answer:
As I have said before in this space, because performance is an interaction of many different factors, it is virtually impossible to discuss it in any specific way in this forum.

I don't understand your situation. When you query a database, you send a SQL query to the database, the database prepares and executes the query, and then returns data. From the way you describe your situation, you are executing the same query that you did initially, so I cannot understand why it would take longer. In fact, most databases would return faster, since relational databases typically cache the SQL statements recently used, and just re-use them if they come back again.

However, your use of the phrase 'whole database' gives me pause. I hope that you are setting the RowFetchMode property to one of the incremental fetch settings. These settings, "Fetch As Needed" and "Fetch Count First," return only the first few rows from a query, so they end up giving faster and more consistent response to a query.

Other than that, I can't think of anything. To make sure that the problem is not in your database, I suggest testing this same query with another tool, such as SQL*Plus for Oracle. If this has the same performance characteristic, look to your database, not OPO.

DevX Pro
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date