Hi Guys, I was wondering whether any DB gurus can help me with a DB design question that I have. I'm currently looking into designing a database for a little app that I have in mind, but I'm a little unsure whether I should have one large table or many smaller tables, which has basically the same schema. Say I'm looking at recording the daily temperature (high/low/average etc) from many locations, would it be better to : 1. Put all the data into one table with all the location information in it. Date, Low, High, Average, City 2. Separate the data into separate tables which represent cities/suburbs (and have another table tracking all the cities and the table name). Table City Date, Low, High, Average Which is the best approach to take? If I take option (1), there'll be performance issues later on (say when I've got a million+ rows and I'm only looking at a particular city). But if I take option (2), then I'll have many tables (hundreds/thousands), but table scanning a particular city would be relatively easy. I'm inclined towards option (2), but I'm wondering whether that is the correct option? Are there any performance issues with databases having lots of tables within them? I'm looking at using MySQL, but am also looking at more databases in general Thanks!