I have two very simple database questions:
1. When does a database get too big, 50 tables, 100 tables, 300
tables? And by database, I mean a single database residing inside of a
DBMS, not each of the separate databases and the tables in each DB
combined. I mean a single database.
2. Are there any rules out there for splitting a database? There are
rules, or guidelines really, for how to organize java programs into
packages and rules for normalizing a database, but are there any rules
for for and when to split a database into separate DB's and/or
separate schemas (in the Oracle or PostgreSQL sense)? Or do you simply
keep building a database until it reaches whatever the table limit is
for your DBMS?
Thanks,
--
chris johnston
www.fuzzylizard.com
"For millions of years, mankind lived just like the animals and
something happened which unleashed the power of our imagination, we
learned to talk."
Pink Floyd
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
