Re: tnsnames vs nameserver

Also, bear in mind that you may suffer a slight additional delay getting a session with the server. Names takes up a bit of time and you feel it when you get frequent short-term sessions. On the other hand, in a large multi-database environment, especially with scads of users, names is awfully convenient.

For absolute, blinding speed, use neither names nor tnsnames.ora, but imbed the tns connect information directly in the v2 connect string. Big hassle to maintain, though.

Roger Snowden
Sr. Systems Engineering Specialist
Oracle Corporation
rsnowden_at_NOTus.oracle.com <-- to reply, remove the obvious

Sybrand Bakker wrote:
>
> Hi Rob,
>
> Big advantages of nameserver: no tnsnames.ora on the client, no need to
> redistribute the file all over the place, if something changes. If you have
> multiple locations, multiple nodes and multiple databases, they will be far
> more easily managed by nameserver. Also: database links are being maintained
> by nameserver automatically, and usually you don't need to define them
> yourself anymore.
> For one database this is of course overkill.
>
> Hth,
> Sybrand Bakker
> Rob Williamson wrote:
>
> > We are about to have an Oracle 8 install done and we were told we needed
> > to decide
> > on tnsnames ( flat file ) or nameserver ( database ) for the Net8
> > install.
> > What does this mean? And how should we decide?
> > Is it based on how many users we will have?
>
> ------------------------------------------------------------------------
>
> Sybrand Bakker <postbus_at_sybrandb.demon.nl>
>
> Sybrand Bakker
> <postbus_at_sybrandb.demon.nl>
> Netscape Conference Address
> Netscape Conference DLS Server
> Additional Information:
> Last Name Bakker
> First Name Sybrand
> Version 2.1
Received on Mon Jan 11 1999 - 21:43:22 CST