Big table or multiple separate tables? (database design question)

Posted by Khou on Stack Overflow See other posts from Stack Overflow or by Khou
Published on 2010-05-30T02:24:12Z Indexed on 2010/05/30 2:32 UTC
Read the original article Hit count: 232

Filed under:
|
|

This is a database design question.

I want to build an invoice web application, an invoice can have many items, and each user can have an inventory list of product items that they can store and choose to add to an invoice item.

My questions are:
1. Should I store all product inventory for all users using my application under one single table? Or have a separate product inventory table created for each user?
2. Is this even possible?

1 table is easier, but what if this single table grows too big, will I have a problem? (primary key INT).

© Stack Overflow or respective owner

Related posts about ASP.NET

Related posts about sql