Lots of tables or one table with lots of TOs? Opinions please!
Puting all the data into ONE table then dividing the table up into TOs using a relation as a filter has advantages.... not the issue...
I have a database which retains graphic elements shown in containers. Which do YOU think would PERFORM better... one table and divide up into TOs or seperate tables??? There's likely to be about 40 tables if I divide into tables. Using a relation as a filter has had a performance hit in past applications in which I have used just 1 table.