|
I'm not sure what the practical upper limits are, I've got one db that's currently at 450mb and performance is not noticeably different than when it was smaller. I'm sure that there are others with much larger db that can weigh-in on this.
The question of splitting dbs has come up before with opinions falling on both sides of the fence.
In the particular example you used, an article reference db, it would probably be best to keep it entact and differentiate catagories (topics or interests) thru the Attributes.
An interesting example of all-in-one or seperate-by-topic would be the case of tracking Books, Movies, and Music. At first glance these would seem to call for different dbs because the Attributes for each would be different, but this can be handled all within one db thru the use of various Forms and Default Child Template assignment.
The all-in-one approach would allow you to "see" the full scope of an individuals contribution across a range of Media (Entertainment).
This is always an interesting topic, design approaches.
|