Jump to content

How many Tables to use?


S Murder
 Share

Recommended Posts

I'm making a site and will have a table that will store a user's contact info, display preferences, and more. In normal form they should all be on the same table, but I anticipate that eventually I might have a hundred rows on each profile table. Aside from being less human readable, will it be any slower? Would it be better to use separate tables with foreign keys referencing a main profile table for different categories of information? If there's less rows, won't SQL use less memory when performing table joins?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...