Two databases or one

[AccessKay]

Hi,

What if you have two organizations and you plan to design a database to do
the same task but within that task, the defined tables will vary because of
unique qualities related to the individual organization. Would it be best to
create separate databases for each organization or keep the two organizations
together?

Anyone know the guidelines related to this?

Thanks for any feedback.

 

[KARL DEWEY]

Ask yourself this - How often will you need the combined data?

 

[Jeff Boyce]

Also ask yourself whether the two organizations ever "share" information
(e.g., both use the same/a common "customer" list...)

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

 

[AccessKay]

Thank you. This answers my question.

Ask yourself this - How often will you need the combined data?

 

[AccessKay]

Thanks. This answers my question also.

Also ask yourself whether the two organizations ever "share" information
(e.g., both use the same/a common "customer" list...)

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.





.