Duz schrieb:
> It's safer to have multiple small databases because of "update anomalies".

Sorry, that's simply wrong (though it may be due to a misunderstanding).

To avoid update anomalies, you normalize a table, which (usually) means
that you split the data into multiple tables.
Having multiple databases doesn't help.

BTW the downside is that you can't JOIN across databases. IOW splitting
into multiple databases is advised if the data should be kept separate.
(Say, a "productive" and a "test" database. Or to enforce safe harbor
constraints, to prevent idle administrators from connecting data that
must remain unconnected.)
I.e. multiple database considerations are about ensuring strategic
properties, while having multiple tables and normalization and avoiding
update anomalies is more "tactical".

Regards,
Jo