UD Connect Vs DB Connect
I am right now working on a proof of concept - DB vs UD. My test case is to connect to a third party Oracle DB (Relational DB). I have very small data set.
So with my testing both UD as well as DB gave me similar performances.
So experts..........has anyone encountered problems with either one of them. I am just trying to draft a tradeoff between both when it come to performance with large data sets.
supriya saxena replied
1.)we use for SAP certified databases this means that the databases that SAP supports.
2.) It supports deltas
3.) It is used for relational databases.
4.) less problems are encountered as compared to UD connect.DBconnect utilizes SAP's basis technology to estabish an interface to a non-SAP database.
5.)It relies onthe dbsl's (shared libraries) that are normally used to make the SAP application run on top of a database. DBconnect is limited to work only with the database types that the SAP application can run on - Oracle, MS-SQL, and the DB2 flavors (400, 390, UDB EEE Aix or Windows).
1.)We use UD connect for other databases which are not SAP supported (not certified)
2.) It does'nt support deltas
3.) It is used for relationaal as well as multidimensional databases.
4.) In this case more problems occur . UDconnect utilizes a different technique altogether, it relies on the adapter framework that exists within the java part of the SAP NetWeaver Application Server.
5.)There are adapters there that can be used together with drivers to establish an interface with non-SAP systems. You can use ODBO, XMLA, or JDBC drivers together with these SAP adapaters to build the interface. Thus, UDconnect is open to intreface with a wide range of system types - there are more than 200 JDBC drivers available from Sun Microsystems, for all kinfd of systems (Teradata, Sybase, SAS, just to name a few).
In SAP NetWeaver BI 7.0, both scenarios support a remote query scenario, where the data does not have to be loaded into the SAP NetWeaver BI system in order to run queries (although in many cases you will want to anyway). In 3.5, only UDconnect supports the remote query scenario.
If you have the choice between DBconnect and UDconnect, DBconnect is usually the first choice. The interface is more simple (using dbsl's from the basis level of the system), and more mature. This basis technology has existed for more than 15 years, while java is relatively new for SAP and less mature. There are more layers in the interface for UDconnect. If the system you are interfacing with is MS-SQL, DB2 or Oracle, DBconnect is probably the best choice. One complexity that can arise is that if you are on a unix system and you want to use DBconnect to interface with an MS-SQL system - if you use DBconnect, you would need a windows application server in order to run the dbsl's (the windows ones don't run on unix). So in that case, UDconnect could be a viable alternative