Hi All,
Could you pls explain what's the difference between Dynamic RDBMS and ODBC and OCI Loader. Also which stage is preferable and when?
I have used only Oracle enterprise stage as of now so dont have any idea about these stages.
Will it be faster using Dynamic RDBMS instead of OE stage?
Thanks
Difference between Dynamic RDBMS, ODBC and OCI Loader
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Dynamic RDBMS stage is nothing more than a wrapper - the DBMS type determines whether an ODBC driver, an OCI function, a Sybase OC function, etc., gets called.
It will never be faster than the equivalent native interface because it is nothing more than an additional layer of software.
But it's more convenient, particularly for folks like PeopleSoft, where the database type is not known a priori.
It will never be faster than the equivalent native interface because it is nothing more than an additional layer of software.
But it's more convenient, particularly for folks like PeopleSoft, where the database type is not known a priori.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 62
- Joined: Sat Mar 07, 2009 4:59 am
- Location: Chicago
- Contact:
Based on versions
![Laughing :lol:](./images/smilies/icon_lol.gif)
Hi
We have so many sources sqlserver, oracle, db2, informix ..etc
initially we have OCI stage, with this stage we will connect up to particular databases, for example older datastage versions can not connect to oracle 10g, because at that time that verison of oracle is not developed, so with OCI stage we can connect up to some versions of databases based on the datastage version, this is having rich performance, so for avoiding this we have ODBC stage, from this we can connect to any type of database and any version, because this is related to system and it connects based on system connection, but this is poor performance, for avoiding all these we have Dynamic RDBMS, it is more popwerful for connecting with any version and with any database and it is having great performance, final conclusion is
1.if ur OCI stage supports your database version use OCI
2.if not suports go for Dynamic RDBMS
3.if any of the stage can not supports for connecting certain databases then go for ODBC stage.for example ODBC stage is used for connecting Excel and MsAccess
hope this will useful
Thanks
Suresh Reddy
ETL Developer
Research Operations
"its important to know in which direction we are moving rather than where we are"
ETL Developer
Research Operations
"its important to know in which direction we are moving rather than where we are"
By purchasing a Premium Membership:shalini11 wrote:Sorry, I am not able to view your full answer.
Some premium content button is displayed. Could tou pls tell how can I view your answer
premium_membership.php
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Re: Based on versions
This is simply... incorrect... on many different levels.sureshreddy2009 wrote:initially we have OCI stage, with this stage we will connect up to particular databases, for example older datastage versions can not connect to oracle 10g, because at that time that verison of oracle is not developed, so with OCI stage we can connect up to some versions of databases based on the datastage version, this is having rich performance, so for avoiding this we have ODBC stage, from this we can connect to any type of database and any version, because this is related to system and it connects based on system connection, but this is poor performance, for avoiding all these we have Dynamic RDBMS, it is more popwerful for connecting with any version and with any database and it is having great performance
![Confused :?](./images/smilies/icon_confused.gif)
The OCI stage is a 'native' stage and thus connects to Oracle using the Oracle client software installed on the server. There's no issue connecting to 10g if the correct client is used, even in older versions. The days of ODBC automatically meaning "poor performance" are long gone and there's no magical "power" or "great performance" in the DRS stage, something Ray notes in his post.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
At the IBM on Demand conference last October, three DataStage engineers presented a session about which stages were the fastest. They stated the Oracle and DB2 Connector stages were the best, followed by either the ODBC or native stages. They specifically stated the ODBC stages were now as fast as the Oracle Enterprise or DB2 Enterprise native stages. There was supposed to be a "Connector Job Migration Tool" released to help migrate from the old stages to the new connector stages for the best performance. Has anyone seen that tool?
For reference, the session at IoD was TSB-1001 - "Expert: Mastering Database Connectivity with InfoSphere Information Server."
For reference, the session at IoD was TSB-1001 - "Expert: Mastering Database Connectivity with InfoSphere Information Server."