Re: same application on multiple schemas

In article <ujLDl.13115$%54.9073@xxxxxxxxxxxxxxxxxxxx>,
maustin@xxxxxxxxxxxxxxxxxx says...>
Jeremy wrote:
In article <M7IDl.4500$im1.4076@xxxxxxxxxxxxxxxxxxxx>,
maustin@xxxxxxxxxxxxxxxxxx says...>
Alberto wrote:
Hello, I'm designing a new big application.

The application will be instantiated for multiple users. Each
application must have its own "database", or schema, Oracle speaking.

How many users per schema? This "scheme" sounds like a disaster waiting
to happen. Do they need separate schemas or do they need separate
databases instances?



Why should it be a disaster waiting to happen? Suppose you were
providing and appplication for multiple customers on a single database.
And suppose one of those customers used the system far more heavily than
other customers and it was decided to separate that user on its own

There are CPU/performance governors for that.

database or server? Having a schema per customer then makes it easy to
move it to another location.

or so you think. If you gauge your customers correctly, you will build
the infrastructure to handle any workload prior to deployment.

You may the same app used by a 10 user company or 500 users. A
customer's use may grow far more rapidly than ever anticipated.

> Another valid scenario might be that the
customer starts off with the system hosted by a supplier but wishes an
option to host on its own environment down the line.

given your initial post,

It wasn't my post, I was just commenting that I can think of a number of
sceanrios where it provides great flxeibility - really to counter your
"disaster waiting to happen" which I still believe to be OTT.


--
jeremy
.

Relevant Pages

  • Re: Migrating a system incrementally. Was: Re: Static vs. Dynamic typing (big advantage or not)
    ... >>Our customers are large ... >>to the new schema at a rate of about two million ... we automate all this stuff in our lab. ... > ability to upgrade its database, then run the kind of version comparison ...
    (comp.object)
  • Re: Migrating a system incrementally. Was: Re: Static vs. Dynamic typing (big advantage or not)
    ... >>Our customers are large ... >>to the new schema at a rate of about two million ... we automate all this stuff in our lab. ... > ability to upgrade its database, then run the kind of version comparison ...
    (comp.programming)
  • Re: same application on multiple schemas
    ... The application will be instantiated for multiple users. ... application must have its own "database", or schema, Oracle speaking. ... providing and appplication for multiple customers on a single database. ... And suppose one of those customers used the system far more heavily than ...
    (comp.databases.oracle.server)
  • Re: same application on multiple schemas
    ... application must have its own "database", or schema, Oracle speaking. ... Suppose you were providing and appplication for multiple customers on a single database. ...
    (comp.databases.oracle.server)
  • Re: Java is becoming the new Cobol
    ... In the Unisys 2200 environment using their Network Database Server, you get a schema work area depending on how you invoke the schema. ... However, it not only copies the schema area into the program, but the "DMCA" (Database Management Communication Area - basically, the block of information that holds your connection state) is copied in too. ... So, you're left with working-storage, which makes it visible to your program only, or common-storage, which makes it visible to programs linked in. ...
    (comp.lang.cobol)