Re: MTS/Oracle8/ODBC

Sorry to reply to another reply, but I lost the original message. Looks like it is NT, by the SQL*Server reference.

One of the common problems in NT is to let the DNS do the TCP/IP name resolution for ORACLE's SQL*Net. Set your host string in the tnsnames.ora file to the IP number for the server. Do this both in the server and the client. AUTOMATIC_IPC doesn't really help,so use the IP number.

Also make sure you create a pool of SQL*Net connections. There is a parameter for listener.ora that does this, but I can't remember which one it is. Look it up in the man pages.

You need this SQL*Net trick on both standard SQL*Net connections and ODBC connections, with the added problem that ODBC will also slow you down further...

MTS won't help as in NT it is not needed.

HTH
--
Cheers
Nuno Souto
nsouto_at_nsw.bigpond.net.au.nospam
Is there a nospam domain?
http://www.users.bigpond.net.au/the_Den Leonard F. Clark <leonard_at_lf-clark.prestel.co.uk> wrote in message news:3799ae66.5143075_at_news.prestel.co.uk...
> >Although the performance of both databases is comparible, there is one area
> >where using an Oracle database is proving much slower. This is caused when
> >establishing an ODBC connection (using Microsoft's ODBC driver for Oracle)
> >from MTS. It takes AGES (about 2secs)! This proves to be a problem because a
> >new connection is required *per process* - and my application uses many
> >processes (many MTS packages) - so, if a user has been hanging about for a
Received on Sat Jul 24 1999 - 08:31:08 CDT