Howdy, Stranger!

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

Categories

MySQL Size Efficency

zapperonzapperon Member Posts: 88
I was ordered to design a database where I have some knowledge about but am not that good. Which I did ad it has 13 tables and +- 16 referential links. These tables were designed so that they could hold for the beginning 40000 records. I estimate the total size of the data not being bigger theb 100MB for the beginning. Now the person who designs the frontend in PHP says No.1 the database can not handle a query efficiently(fast) due to its complexity and that he has to restructure the whole database so it fits into only 4 tables. This will increase the size quite a lot. Now I am wondering : I heard don't know if it is true that YAHOO is usign MySQL. So I am wondering does YAHOO not have quite a large amount of record and data , and I guess they must also not have a very simplified database structure or do they ??? The question revolves around the though that I though a database is most efficient when it follows those 3 norms thingy(like I said not an expert database designer). Could anybody give me some extra info please.
Zapperon
ewu@webmail.co.za

Comments

  • JonathanJonathan Member Posts: 2,914
    : I was ordered to design a database where I have some knowledge about
    : but am not that good. Which I did ad it has 13 tables and +- 16
    : referential links. These tables were designed so that they could
    : hold for the beginning 40000 records. I estimate the total size of
    : the data not being bigger theb 100MB for the beginning. Now the
    : person who designs the frontend in PHP says No.1 the database can
    : not handle a query efficiently(fast) due to its complexity and that
    : he has to restructure the whole database so it fits into only 4
    : tables. This will increase the size quite a lot. Now I am
    : wondering : I heard don't know if it is true that YAHOO is usign
    : MySQL. So I am wondering does YAHOO not have quite a large amount of
    : record and data , and I guess they must also not have a very
    : simplified database structure or do they ??? The question revolves
    : around the though that I though a database is most efficient when it
    : follows those 3 norms thingy(like I said not an expert database
    : designer). Could anybody give me some extra info please.

    MySQL can work with millions of records if need be so 40000 records ain't bad. Depends how fast you need it really, though personally I'd virtually never comprimise normalization for a bit of extra speed (which sounds like the approach that the front end programmer may be suggesting). Though that's me. :-)

    I've speeded queries up more than tenfold by adding a couple of carefully placed indexes, so I'd try getting the relational design going before scrapping it for some approach that will probably result in loads of redundant data.

    Jonathan

    ###
    for(74,117,115,116){$::a.=chr};(($_.='qwertyui')&&
    (tr/yuiqwert/her anot/))for($::b);for($::c){$_.=$^X;
    /(p.{2}l)/;$_=$1}$::b=~/(..)$/;print("$::a$::b $::c hack$1.");

Sign In or Register to comment.