Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

An efficient database (to join or not to join?)

Status
Not open for further replies.

monkey64

Technical User
Apr 27, 2008
69
GB
I have a stock table in my database with 20k records.
I'm not experiencing any performance issues.

At this stage, I could split this large table into 3 smaller tables. One for stock, price, and category and simply join them in a query.

Is there a real performance issue leaving one large table or is this really not necessary?
 
My table is 2.3 MB in size. I would consider that large!
At what point would you consider spliting the tables?



 
2.3MB is far form being large. I have pictures that are larger than that.

Once you get to millions of rows, and tables that are about 500MB to several Gigabytes in size it would be considered large.





----------------------------------
Phil AKA Vacunita
----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

Behind the Web, Tips and Tricks for Web Development.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top