Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Mazenx
Starting Member
5 Posts |
 Posted - 2011-03-20 : 04:35:37
|
| hello...I have a table called Images which has images data , now...I want to create another table to hold date for image thumbnails , I have four thumbnail sizes so basically four types of thumbnails...I was thinking to create a thumbnails table , but this table is going to be large soon...so without thinking It would be later slow to have a query joining between two tables...so I was thinking to create another four tables for each thumbnail type , but that seems somehow miserable....so my final thought was to create two tables for the thumbnails , one for the smallest thumbnail and the other for the other sizes(which are less frequently used )....can someone tell me what is the best design for ths ??? |
|
|
Bustaz Kool
Master Smack Fu Yak Hacker
1834 Posts |
Posted - 2011-03-21 : 11:17:04
|
| Joining between two tables should not be a slow operation, provided the indexing has been set up properly. My real question, however, is why do you need a second table to hold the Date of the images? My larger question is what makes the images different conceptually? Are they used for the same purpose, just different sizes? Also, when you say that the table will be "large", can you quantify that? Number of rows? Size of a row?=======================================Elitism is the slur directed at merit by mediocrity. -Sydney J. Harris, journalist (1917-1986) |
 |
|
|
X002548
Not Just a Number
15586 Posts |
|
|
|
|
|
|
|
database design question