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

[monkey64]

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?

 

[r937]

it is not necessary

10k rows is a small table

r937.com | rudy.ca
Buy my new book Simply SQL from Amazon

 

[monkey64]

My table is 2.3 MB in size. I would consider that large!
At what point would you consider spliting the tables?

 

[r937]

At what point would you consider spliting the tables?

when i run out of space on the disk

r937.com | rudy.ca
Buy my new book Simply SQL from Amazon

 

[vacunita]

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.

http://behindtheweb.blogspot.com/