Re: oracle names - pros/cons

Ed Stevens wrote:
>
> I have been tasked with researching the pros and cons of using Oracle
> Names Servers vs. TNSNAMES files. I know that Oracle Names is supposed
> to give you a single point of maintenance for database name resolution.
>
> In our environment (Oracle on NT, NT clients), we have used the
> TNS_ADMIN registry key to relocate the SQLNET.ORA and TNSNAMES.ORA
> files to a shared server location. This gives us the single point of
> maintenance offered by Oracle Names. Are there any other advantages to
> O-Names? Maintenance? Admin? Performance? Any disadvantages? I
> would expect it to be a bit of a performance hit over even our server
> shared TNSNAMES simply because it is a more complex mechanism with
> another service running on the server and broadcasting itself over the
> network, but really don't know.
>
> --

A lot of it depends on your environment. Yours sounds pretty simple - all NT. If you have a small number of databases, and they don't change too often, then your current solution sounds fine. If you had a mixed environment (NT, unix, VMS) across multiple sites with a large number of databases (meaning you're probably constantly updating your sqlnet configuration), then Oracle Names sounds like the better choice. Received on Mon Mar 20 2000 - 00:00:00 CST