Does it make sense to create an enterprise database design where there
is 1 table for people, another for addresses, another for
phones...etc. The idea is each dept would contribute to these tables
and then have their own database for specific applications. I'm not a
database expert but this design seems nice in theory but difficult to
use. Anyone else use such a design? Do you like it?
