Too many schemas!

From: Donatella <donatella_at_webadorable.com>
Date: 17 Nov 2002 04:30:41 -0800
Message-ID: <ff4c959.0211170430.4cea7752@posting.google.com>

I am working on a three-tier architecture for a web-hosted application, with browsers at the front, J2EE in the middle, and Oracle at the back.

My experience is mostly in J2EE and until now I have only worked with single-client models.

This application is intended for many clients - each with their own set of users - working with their own separate data.

Initially I was imagining having many identical schemas, one for each client.

But with 500-1000 clients this seems unmanageable when it comes to implementing future changes to the database.

Should I be considering ONE schema shared by all the clients?

That would mean tagging ALL the records with client IDs which would predicate all data queries and transactions.

This must be a common issue with web-hosted applications.

Any pointers to online resources and/or books which deal with this would be much appreciated.

Many thanks!

Donatella Received on Sun Nov 17 2002 - 06:30:41 CST