OT: problems using multiple databases

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-

A couple of quick thoughts of the top of my head...

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.

--
Lawrence - Team Macromedia
Cartweaver - Shopping Cart Solution for DreamweaverMX
http://www.cartweaver.com
news://support.cartweaver.com/cartweaver



"-D-" <webforumsuser (AT) macromedia (DOT) com> wrote

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-

Hi Lawerence,
Thank you for replying my post. I appreciate your input. I currently came
into a job where the legacy web application is running on several FoxPro
databases and as you pointed out, there appears to be lots of data integrity
problems with duplication of fields, invalid records and a plethora of other
problems. I'm not a database application developer, but do have a reasonable
understanding of the back-end from a web application standpoint as I've built
several smaller size web applications using ASP and driven on Access or SQL
Server.

I'm trying to help encourage them to move the legacy system over to a stable
application and re-deploy on one database application. Possibly PHP and
MySQL? Or ASP and MySQL? I very much appreciate your input.
-D-