Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 479
  • Last Modified:

Speeding up Queries that have CachedUpdates

Using Delphi 3, BDE 4.51 to get at paradox/foxpro tables with LocalSQL.

Recently, I had to move my Queries over from live to CachedUpdates.  As soon as I set the TQuery.CachedUpdates property to True, the performance slows to a crawl.

Are there some settings that speed that up?  Either in the BDE or an object?

Thanks,
joe
0
greendot
Asked:
greendot
1 Solution
 
oberdanCommented:
Hello greendot,

      There are many ways to improve queries. Here go some ideas:


1 - Use the Prepare method of TQuery objects before opening them. It sends an SQL query to the database engine for parsing and optimization. If Prepare is called explicitly for a query that that will be executed more than once, Delphi sends only the query parameters - not the entire text - with each successive execution. This make query operations run faster.

2 - UpdateMode - TTAble and TQuery have an UpdateMode property. This determines the type of WHERE clause used to perform modifications using dataware comtrols. It defaults to UpWhereAll, which means that BDE generates a WHERE clause that list every column in a table. An alternative (faster) is to use UpWhereCanged setting. It generates a WHERE clause that mentions only the table's key fields along with the fields that were changed.

3 - Schema caching - BDE supports schema caching -  storing structural information about database object locally. Enabling schema caching can reduce the queries sent by your app to server to retrieve database catalog information. This can speed up your app significantly cause BDE is not forced to constantly re-retrieve meta-data from server.
You can enable schema caching in the BDE Admnistration Utility. There are four settings that are related to schema caching.

ENABLE SCHEMA CACHE                  Enable/Disable Schema Caching

SCHEMA CACHE SIZE               Number of tables for witch to                                     cache schema data

SCHEMA CACHE TIME               Specifies the number of seconds
                                to cache schema information

SCHEMA CACHE DIR                directory to store schema info.


Sorry if i was a bit verbous...

I hope it can help you
   
                         []'s
                                 Oberdan

0
 
greendotAuthor Commented:
I already had those set. :)

The schema cache is for a different type of database setup.  This is all local, no servers.  We get to use SQL on top of local tables.  It's neat, but sometimes it's a pain in the you-know-what.  

The BDE does not give you many settings when doing this LocalSQL stuff.

Thanks for trying.  :)

-gd
0
 
manolis_afentakisCommented:

i don't know if u tried this:

A         set cached updates only before updating ,
B         or read this about index performance (for local databases:)

 For each field you intend to search or query, you need a:  (1) maintained, (2) case-
sensitive, (3) single-field secondary index.  This is essentially the only type of index that a
query will use.

 Maintained indexes -require- that there be a primary key.  In PxWin you can simply use
the "autoincrement" field-type to create one if you don't have one.  Paradox for DOS users
have to do the same thing manually but it's still worth doing so that you can get the other
indexes.

 The necessity of indexes can be demonstrated by this:  in your Yellow Pages, please find
the first Accountant.  (That was easy.)  Now find Joe Smith, CPA...  (Hope he's under
Accountants!) Now find the phone-number 543-2109.  :-)  A computer will obligingly attempt
any one of these operations even though you, the impatient human, would never subject
yourself to the same labor!

 Regardless of what software you use, indexes are THE most important factor in database
performance and you should make yourself very, very familiar with them.  Given the extreme
overhead of transferring large amounts of unwanted data through a network, the overhead of
maintaining the indexes pales in comparison.


0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now