In response to the Oracle advertisement, here are Facts on the subject as put up by Jeff Nolan of SAP Ventures - all based on "recent research"

• The Gartner report in question also stated that "less than 10 percent of Oracle's installed base will be live on v.10 of 11i by the end of 2005 (0.7 probability)." What Oracle is attempting to do is claim that all 10 versions of 11i are current releases and by adding up the percentages they get to 94% (which is actually qualified as a "predicted" number by the end of 2005 and not an actual... remember the report in question was authored in March of this year.)
• Oracle's de-support of 10.7 in June 2003 essentially forced an upgrade. The Gartner report that Oracle uses states that Oracle had "driven users from v10.7 to 11i".
• 
  
  • SAP is providing end-to-end support for every current product in our portfolio through the end of 2009 and in the case of our ESA platform the support commitment goes through 2013.
  • In the March '05 Gartner report it was also noted that "SAP's flexible maintenance option will provide customers that want to embrace SAP's Enterprise Services Architecture (ESA) with an option to wait until it matures within future versions of mySAP ERP. This option also allows the deferment of the upgrade project costs for an incremental increase in maintenance fees."
• The poor quality of 11i was major factor in the frequency of upgrades following the initial release of that product
• 
  
  • 5000 bug fixes were released in the first 6 months (Forrester, 2001)
  • It took two years and six releases before it was viewed as stable Gartner, 2002). To add insult to injury, Oracle de-supported the 8i database this year meaning that customers who were on the minimally stable 11i.6 release were forced to upgrade again.
  • 11.9, which came out in 2003, still had bugs according to Gartner (2003), and their most recent release will probably be identified with bugs, after it has been out long enough for customers to try it.
  • Oracle forced customers to upgrade to obtain bug fixes by sending out family packs with patches and bug fixes
  • According to an AMR study (2004), Oracle customers were more likely than average to identify bug fixes as a reason for upgrading.
• SAP customers do not upgrade as often as Oracle customers because of the value its software is already delivering. According to AMR, the maturity, or rich functionality, of SAP's software reduces the necessity of customers having to upgrade. In addition, according to AMR, it better enables SAP customers to upgrade to achieve desired changes in business processes.
• According to AMR (2004), Upgrades cost an average of $1839 per user and one man-week of labor for every business user. Upgrades, even when they provide value, are disruptive to customers and SAP understands this.
• With Fusion, Oracle customers will have to undergo a number of upgrades similar to what occurred with e-Business Suite, which was a smaller undertaking than Fusion. This is reflected in Gartner's (2005) and Forrester's (2005) cautions to customers about the implications for Fusion of Oracles history of poor quality and immature software.
• SAP's approach is to make each software version a high quality product, with mature functionality that works as promised. SAP has a stringent process for quality, and does not release a product until it has been thoroughly tested. Analysts, (e.g., Giga, AMR) agree that SAP leads in delivering quality software.
• This highlights another difference between SAP and Oracle. When SAP stated it would invest in Research and Development, at the expense of increasing its own respectable profits Oracle's CEO chided SAP for this customer commitment. "Mr Ellison ridiculed SAP's decision to sacrifice short-term profit growth. 'We're (earnings per share) obsessed,' he said."

Source: 1Prashanth RaiTag(s):Oracle, Gartner, SAP