|
|
Posted by J.O. Aho on 05/11/05 07:26
cover wrote:
> If you're writing many databases that aren't necessarily associated
> with each other (ie parts, vacation days, how you like your steak
> done, and school you attended, etc; as examples), does it make more
> sense to have one database name and several tables for the data topics
> above OR multiple databases since they aren't associated with each
> other?
>
> It would SEEM easier to have a single database with multiple tables
> from a data management perspective as long as there's no risk of data
> integrity issues as a result of having multiple tables under one
> database header. TIA
If you have data some are somehow releated to eachother, as they are managed
with the same tool, then one database will be IMHO the best option.
The integrity of data can be set by premissions for the users, so that an user
don't have access to all the tables, while another may have access to all the
tables.
//Aho
Navigation:
[Reply to this message]
|