| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| what is the difference between thin vs thick in oracle 10g |
« View previous topic :: View next topic » |
| Author |
Message
|
| AKSHAYA |
 Posted: Fri Sep 07, 2012 3:34 am Post subject: what is the difference between thin vs thick in oracle 10g |
 |
|
Newbie
Joined: 24 Dec 2008
Posts: 9
|
Hello ,
I have a scenario - Broker needs to access the Neon rules & formatter Database from a different remote server using the odbc driver ,its taking more time for a simple transaction.I have came across the some of the discussion -on thin vs thick oracle clients. Is it really make a impact for the performance ? Can anyone though some lights on this.
Any thoughts will be appreciated !!
Thanks,
Akshaya |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Fri Sep 07, 2012 5:29 am Post subject: Re: what is the difference between thin vs thick in oracle 1 |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| AKSHAYA wrote: |
| thin vs thick oracle clients. |
Not relative to WMB. Although you will probably get 0.000025 percent better performance from the thin driver comparing between the same non-WMB application that can drive both.
Oracle's JDBC Thin driver uses Java sockets to connect directly to Oracle. It provides its own TCP/IP version of Oracle's SQL*Net protocol. Because it is 100% Java, this driver is platform independent and can also run from a Web Browser. This driver is a Type 4 (Proprietary Protocol-Net) driver and is written in 100% pure Java making it platform independent. It allows a direct Connection to the database. It implements the TCP/IP protocol that emulates Oracle's Net8 and TTC (the wire protocol of OCI) on top of Java sockets. Java applets are good candidates that make use of this driver. This driver gives the maximum portability.
Oracle Thick: This is a native-API Type 2 driver that is suited for client-server Java applications. It is Oracle platform-specific and requires an Oracle client installation. This driver converts JDBC calls into calls to the Oracle Call Interface using native methods. These calls are then sent to the Oracle database server using Net8. These drivers support protocols such as IPC, named pipes, TCP/IP, and IPX/SPX. This driver gives the maximum performance for an Oracle client application.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Sep 07, 2012 5:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You can only use the Database Drivers that are Supported to talk to the NEON database.
You will get better performance long term by MIGRATING from using NEON.
You should model your data in MRM instead, so that when you migrate to v8 you can migrate your data to DFDL and get great performance.
You should have migrated off of NEON at least two years ago. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
