Re: Oracle licensing

Oracle no longer sells concurrent user licenses. However if you already own a concurrent user license, Oracle measures total users, not total connections. Thus, even if you use connection pooling ot multiplexing, or MTS. etc, you need to count end-users, not connections.

Walter T Rejuney <BlueSax_at_Unforgetable.com> wrote in message news:3A9F9B3B.40CA347A_at_Unforgetable.com...
> I have a question about Oracle licensing policies.
>
> Suppose I have a database running on a server. This database serves
> provides OLTP services to a client application. If I write the client
> application to use a DCOM object such that the first time the client is
> started the DCOM object will create a connection to the database and
> each subsequent lauch of the application on other workstations would
> share the original DCOM object which would then broker transactions for
> the desktop application. Finally, suppose there are 200 client
> workstations which could potentially share this DCOM object
> concurrently.
>
> The other choice would be simply to have each workstation have its own
> COM object which would connect to the database via
> multi-threaded-server.
>
> Since there is really only one connection with the DCOM object, would
> that require one user license or would it be no different then using COM
> object in that the licensing requirements would be based on the maximum
> number of concurrent users regardless of how many actual connections to
> the database occur?
>
> Appreciate any answers.
Received on Sat Mar 03 2001 - 11:55:32 CST