Hello, I'm planning out a database, however, it has the potential to be quite large, and I don't know how large is too large. While I've worked with MYSQL quite alot, I have never really come across the best database planning, so my plan below is up for criticism. Essentially, I will have one PARENT database containing general data about a particular object. There will then be another CHILD database that will have data about objects linked to the parent object. [i][You can think of it like the PARENT is a forum post, and the CHILD are the replies, though I'm not designing a forum, but you get the idea].[/i] My situation is that the PARENT database could have thousands of objects/rows. Each parent object could have 5-100+ child objects. So, if the PARENT database holds 6000 objects, and each object has 60 CHILD objects, that would make the PARENT db with 6,000 rows, and the CHILD database with 360,000 rows; all with the potential to grow 2, 3, 5x the size. I have never dealt with a database quite of this size. Is this too much and should I think about another method to break up the CHILDren db's? Thanks, Rege