Multiple Databases??

[Guest]

When would I want to set up separate databases instead of one overall
database?

My initial intention was to set up a marketing database to keep track of our
mailing list and what mail pieces were sent, to whom, when, etc. But then I
thought I should expand the database to track JOB information when someone
responds to our marketing. Now I'm wondering whether they should just be 2
different databases.

What do you think? If I set them up as 2 different databases, can I link
them? (customer or 'contactid' being the field in common).

 

[Guest]

Databases normally exist in 2 parts, a front-end which contains the
processing logic and a back end which contains the data tables. These two
parts are linked together. There is no reason why you cannot have multiple
back-ends. Also, there is nothing to prevent multiple front-ends from
accessing the same back end.

There are many factors involved in deciding whether to combine databases or
keep them separate. Does one person update the job database and the marketing
database, if so it may be less cumbersome to have them combined. Do reports
need to combine information from both functions? Another issue is security,
are the security needs of both functions and their data the same?

Dorian

 

[chris.nebinger]

Things to consider:

An MS Access database is limited to 2 GB in size. If you are going
over that amount, then you will need to break it into two databases.

Security: Without implementing user-based security, seperating
databases is an easy way to implement security.

You can have the the Customer/Contact table linked to the second
database and utilized referential integrity.

Using two databases allows for more people to access the data. Most
people recommend only having maximum number of users at 5, although
Access supports much more.

Having all data in one place makes backups easier.

Having all data in one place increases risks of data loss due to
corruption.

Two different front ends would allow for different people to access
different aspects of the application. However, if one person has two
different roles, than one system would be much easier.

Those are just some thoughts off the top of my head.


Chris Nebinger

 

[Guest]

Thank you for the replies. You've answered my question, now I have a bit more
thinking to do to decide which way to go. Thanks for the help!