Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Oracle connection
- Thread starter Arde
- Start date
Hi,
Service usually means what TNSNAMES.ORA alias to use or what Oracle instance to connect to - not sure since I always use the 'native' Oracle Server connection and not OLE DB.
Why not use that instead?
![[profile]](/data/assets/smilies/profile.gif "[profile] [profile]")
To Paraphrase:"The Help you get is proportional to the Help you give.."
Service usually means what TNSNAMES.ORA alias to use or what Oracle instance to connect to - not sure since I always use the 'native' Oracle Server connection and not OLE DB.
Why not use that instead?
To Paraphrase:"The Help you get is proportional to the Help you give.."
IanWaterman
Programmer
When using OLE DB you should not need service or rely on TNS names.
Should only ask for Server, user name and password.
Ian
Should only ask for Server, user name and password.
Ian
Hi,
For an Oracle OLE DB, the 'server' is specified by using the TNS alias...Also,the Oracle client and its tnsnames.ora file must be on the maching requesting the connection.( There are some 'wire protocol' ODBC drivers that do not need an Oracle client, but OLE DB does.)
The 'native' Oracle Server connection is superior to either in many cases.
To Paraphrase:"The Help you get is proportional to the Help you give.."
For an Oracle OLE DB, the 'server' is specified by using the TNS alias...Also,the Oracle client and its tnsnames.ora file must be on the maching requesting the connection.( There are some 'wire protocol' ODBC drivers that do not need an Oracle client, but OLE DB does.)
The 'native' Oracle Server connection is superior to either in many cases.
To Paraphrase:"The Help you get is proportional to the Help you give.."
IanWaterman
Programmer
Hi Turkbear
Thats interesting (you learn something new every day). If you need a TNS for OLE DB, then it would seem that OLEDB is pointless and you might as well use the superior Native connection.
Not on Oracle at present, but using OLE DB to MS SQL server 2005. In this case it is much simpler no need for machine specific ODBC or native connections. Wrongly assumed Oracle would be the same
Ian
Thats interesting (you learn something new every day). If you need a TNS for OLE DB, then it would seem that OLEDB is pointless and you might as well use the superior Native connection.
Not on Oracle at present, but using OLE DB to MS SQL server 2005. In this case it is much simpler no need for machine specific ODBC or native connections. Wrongly assumed Oracle would be the same
Ian
Hi,
In most cases, yes, the Native Oracle Server is the way to go..there are some cases ( like using VB or .NET apps to run the reports when OLE DB ( and other ADO style ) connections are the only option ( unless you have installed the Oracle .NET assemblies of course)).
The 'wire protocol' ODBC drivers ( and CR's more recent downloadable ones have been that kind, I believe ) are better than OLE DB, since no Oracle client software is needed and little overhead is added.
To Paraphrase:"The Help you get is proportional to the Help you give.."
In most cases, yes, the Native Oracle Server is the way to go..there are some cases ( like using VB or .NET apps to run the reports when OLE DB ( and other ADO style ) connections are the only option ( unless you have installed the Oracle .NET assemblies of course)).
The 'wire protocol' ODBC drivers ( and CR's more recent downloadable ones have been that kind, I believe ) are better than OLE DB, since no Oracle client software is needed and little overhead is added.
To Paraphrase:"The Help you get is proportional to the Help you give.."
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question