On Mar 23, 2004, at 10:53 AM, Mike Nolan wrote:
>> Has anyone ever heard of using a separate administration database
>> which is used to modify business data, and then periodically that data
>> would be pushed out to the other database running the customer web
>> application? Does this idea make any sense at all?
>
> This sounds like a task for separate schemas rather than for two
> separate databases. The advantage of the former is that you can
> move data between the two in SQL fairly easily, moving data between
> two independent databases is (currently) more challenging.
One of the reasons this idea was suggested was because my client is
concerned that its "crazy" to be modifying business data in a system
that is running and processing purchase transactions. And I'm
wondering whether or not this is even a concern when most people build
this type of application. I think its going to be painful to keep
track of changes between the two databases (or schemas if you prefer).
It sounds like this would be highly prone to errors and cause more
problems than it solves.
Thoughts?
-M@
