Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Categories

Welcome to the new platform of Programmer's Heaven! We apologize for the inconvenience caused, if you visited us from a broken link of the previous version. The main reason to move to a new platform is to provide more effective and collaborative experience to you all. Please feel free to experience the new platform and use its exciting features. Contact us for any issue that you need to get clarified. We are more than happy to help you.

More more more performance problems.

zapperonzapperon Posts: 88Member
I currently have a database that has 7 tables made using database desktop. Table types I think are .DB Paradox tables .!? Has a total size of 224 MB. Largest table contains +- 300000 records. Now the problem is I am querying on it and it is a simple query eg. "TheName LIKE 'Robert'". This takes forever 1 minute taking into account that the user will want to query a couple of times per minute.

Problem Source No.1 : I am running the database on , and it will have to run on computers under 500MHz with maximum 64 MB. Not much I can do about that.

Problem Source No.2 : Might be the database or not ? I have no idea. So is there an alternative to the BDE in the same price range that delivers better performance ?

Proble Source No.3 : There are not enough tables. Can a higher relationship count make the database more efficient.

Can anybody give me advice ?
Zapperon
ewu@webmail.co.za

Comments

  • injektiloinjektilo Posts: 113Member
    1. your database should be normalized, sometimes this is not possible however, but make it as normailized as possible.
    2. use secondary maintained indexes on fields you are searching for, this will speed things up.
    3. i've found that running a query is much slower then looping through the records and selecting them yourselve. only use querys, if the selection code of a record grows to big or difficult.
  • mpagnanmpagnan Posts: 2Member
    More information is needed. For example, are you using indexes? Have you indexed starting with you least used key? Is the database on a network and accessed by many users over the net? If so, are you locking the database? I have had no problem with even larger databases using Paradox tables; however, I would tend to migrate away from Paradox tables to something like MySQL or PostgreSQL when the tables get up to your size.
  • zapperonzapperon Posts: 88Member
    Thank you for all your help. I can not create additional indexes as this would make the database to big for my purposes. I have decided that I will now learn MySQL and migrate / move over to it. Does anybody know what the licensing agreement is when distributing it with a commercial application ?

    Zapperon
    ewu@webmail.co.za

Sign In or Register to comment.