OT: problems using multiple databases

message from -D- on 19 Jul 2004

I'm not too familiar with database application building. From what I know, it
is best to build one database with all necessary tables and relationships.
What is the downside or problems with having multiple databases within a site?
Say you have 5 or 6 FoxPro databases within a site that are routinely opened
simultaneously. I'm trying to get a better understanding of the problems
related to this type of scenario and the benefits to using one database for all
access. Thanks for any input.
-D-

Lawrence TMM replied to -D- on 19 Jul 2004

First off, there is no way to enforce referential integrity, well you could
do it in your code but it's likely this would fail somewhere down the line.
As a result of this you are very likely to end up with duplicate data and
orphan records.

This is sure to slow the application and most likely introduce instability.

Just as an aside, Fox Pro, can not be considered a viable option as a web
database. If you are self-hosting you might get away with it, but if you are
on a shared host, it just aint going to happen.

Trying to support a system, like you are suggesting would become a holy
nightmare! If you go this route an prescription to battle Acid Reflux
Disease will definitely be in order.

My earnest suggestion is develop a single database in a widely supported
platform, preferably SQL Server or even My SQL version 4 or above. Doing so
will save your application, data, your hair, health, and possibly your job.
:-)
Hope this is helpful.

Archived message: OT: problems using multiple databases (Macromedia Dreamweaver Web Design)