Re: Choosing DBMS and architecture for ecommerce website

"Michael Peppler" <mpeppler_at_peppler.org> wrote in message news:<pan.2003.11.03.15.33.00.222843_at_peppler.org>...
> On Mon, 03 Nov 2003 07:08:07 -0800, Alex_Bxl wrote:
>
> > I'm wondering how to design that part, should I store all information
> > on the web host only ? miror that DB every evening on some local DB
> > server to be able to use the data without eating up lots of bandwith ?
> > separate the database in 2 parts ? how to sync and assure integrity
> > then ? having a local DB will also mean the company will have to pay a
> > licence for the DBMS ...
>
> I'd use Sybase, and I'd use replication server to move data from the
> production server (in co-location facility) to the reporting server (in
> the office).
>
> But you can do similar things with Oracle, MS-SQL, etc., although I'd
> personally stay away from MS-SQL due to its being Microsoft-centric (i.e.
> can't scale beyond Intel/Windows type machines)
>
> Michael

Dual DB's aren't really necessary.

Points in favor of 2 DB's

*its standard approach Production and Development DB's
*large reports don't hog resources from live interactions.
*new developments/data are staged in development first, in a secure,

points in favor of 1 DB
*if its accessable from the WEB then developers can work there too. (schema isolation should be as good as DB isolation) *web access means you know when the site goes down.

I've seen both. Received on Mon Nov 03 2003 - 20:34:51 CET