@prefix rdf: . @prefix ns1: . @prefix sioc: . ns1:this rdf:type sioc:User . @prefix ns3: . @prefix foaf: . ns3:this rdf:type foaf:Organization . @prefix atom: . rdf:type atom:Feed . @prefix sioct: . rdf:type sioct:Weblog . @prefix rdfs: . rdfs:label "uda's BLOG [135] description" ; rdf:type atom:Entry , sioct:BlogPost . @prefix dc: . dc:title "SAP, IBM Make Play for Oracle Database Customers With New DB2 Version" ; foaf:maker ns3:this ; rdfs:label "SAP, IBM Make Play for Oracle Database Customers With New DB2 Version" . @prefix dt: . @prefix dcterms: . dcterms:created "2005-04-28T21:52:55Z"^^dt:dateTime ; dcterms:modified "2006-06-22T08:56:58-04:00"^^dt:dateTime ; sioc:id "cb0d0fc24a9d6398dfa0a16e8527b0af" ; sioc:link ; sioc:content "<font size="2">\n<p><a href="http://ct.enews.eweek.com/rd/cts?d=186-1965-11-96-81585-221904-0-0-0-1">CNET reports</a>:</p>\n<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">\n<p>There are a whopping <u>44,000 SAP customers</u> running on Oracle databases, and IBM wants them. To get them, for the first time ever, it's optimized its enterprise database for a specific vendor's applications. The new version of DB, 8.2.2, will include a slew of SAP-optimized features, including self-tuning, self-configuration, silent install, dynamic storage allocation and more. </p></blockquote>\n<p dir="ltr">Wouldn't SAP be better served by simply making their application database independent via <a href="http://uda.openlinksw.com/odbc/">ODBC</a>? This process really could have&nbsp;commenced years ago and prevented today's dilema: Your Partner has&nbsp;become Your most aggressive Competitor! </p>\n<p dir="ltr">SAP tuned for specifically for DB2 or SAP tuned likewise for Microsoft SQL&nbsp;simply reeks of: "Same Sh*t different Pile".&nbsp; Microsoft and IBM will emulate Oracle in due course regarding their assault on SAP's market if DBMS specificity remains the SAP data access API strategy (this is a simple fact).</p>\n<p dir="ltr">SAP should be using its quest for DBMS independence to stimulate or contribute ODBC enhancements&nbsp;(should ODBC be lacking in areas critical to its application needs; it is available in <a href="http://www.iodbc.org">Open Source form</a>&nbsp;and across all major platforms).&nbsp;Should the ODBC API not be the problem, then it can&nbsp;push ODBC Driver vendors (DBMS vendors such as IBM included) to get their Drivers in shape (should they be lacking, I know <a href="http://uda.openlinksw.com/odbc ">our ODBC Drivers</a> are absolutely fine for this kind of task).</p>\n<p dir="ltr">Database specificity gets application vendors nowhere.&nbsp;You can only control your business development destiny by being database independent. When applications are database independent&nbsp;the intellectual capital&nbsp;that drives your applications is preserved. This is akin to building physical and logical firewalls around the ecosystem created by your products. This is much better that being a pseudo DBMS engine reseller for a future competitor.</p>\n<p dir="ltr">&nbsp;</p>\n<p dir="ltr">&nbsp;</p>\n<p dir="ltr"></font>&nbsp;</p>" ; atom:title "SAP, IBM Make Play for Oracle Database Customers With New DB2 Version" ; sioc:has_creator ns1:this ; sioc:has_container ; sioc:links_to , , , ; atom:source ; atom:author ns3:this ; atom:published "2005-04-28T21:52:55Z" ; atom:updated "2006-06-22T12:56:58Z" . @prefix opl: . opl:isDescribedUsing .@prefix rdf: . @prefix ns1: . @prefix sioc: . ns1:this rdf:type sioc:User ; sioc:creator_of . @prefix ns3: . @prefix foaf: . ns3:this rdf:type foaf:Organization ; foaf:made . @prefix atom: . rdf:type atom:Feed . @prefix sioct: . rdf:type sioct:Weblog . @prefix rdfs: . rdfs:label "uda's BLOG [135] description" ; sioc:container_of ; atom:entry ; atom:contains .