Jump to content

Recommended Posts

if you had lots of tables then you would be incorporating a lot of joins or numerous commands, which would in effect be the same if not more power intensive as having one tables with many rows.

Keep your tables focused to their task, don't go trying to slim down the DB by making one table keep several tasks data and mysql is developed to handle huge databases with millions of rows

What will make the database take longer to load and pull data from it

 

A database with lots of tables

or

a database with very few tables but a shit load of data in each table?

 

Thanks for your reply

 

Sounds like you're asking if you should use a relational database or not?  Most likely yes, but in some cases no.  Depends on what exactly you're trying to do.

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.