Re: Dedicated Vs. Shared Server Mode

chrisforbis_at_yahoo.com (Chris Forbis) wrote in message news:<f2dc430d.0207110718.7e242ed_at_posting.google.com>...
> That is one of those fun questions you can get all sorts of answers
> for. But dedicated is always faster if setup correctly. But
> dedicated needs more resources. Now it looks like if all that will
> use it is WebSphere, well that is not that many connections. So
> dedicated seems the best with the information you provided.
>

If the number of concurrent sessions is relatively small dedicated servers will work just fine.

> peter.peltonen_at_iki.fi wrote in message news:<agjk54$e5o$1_at_oravannahka.helsinki.fi>...
> > I am creating an initial db with the Oracle Network Configuration
> > Assistant.
> >
> > I am now wondering if I should install the db in Dedicated or Shared
> > Server Mode:
> >

A dedicated server only serves one session. A shared server can serve many sessions. If there are going to be a large number of concurrent sessions, use MTS.
> > The DB is to be serving a WebLogic J2EE Application Server which is
> > talking to it via JDBC. This will be the only client that will be issuing
> > queries to the db.
> >
> > So, in which mode should I install the db in this case? If in Shared Mode,
> > should I use Connection Pooling and if so, what would be the values one
> > might suggest to use with it?
> >

Connection pooling really won't give you more active connections. Shared servers will. But since WebLogic allows you to easily create connection pools you might as well use it, so that you don't have to keep opening and closing connections. Just pay attention to some minor details. A common mistake I have seen is not closing the ResultSet before releasing a connection. Then you'll quickly reach the maximum number of cursors.

> > Regards,
> > Peter
Received on Thu Jul 11 2002 - 23:27:44 CDT