Unicode bloat blights SAP upgrades
Oracle throws the mob a body
Customer Success Testimonial: Recovery is Everything
A relatively small change to the way SAP represented characters four years ago is threatening to complicate upgrades to the latest edition of its software.
SAP's implementation of Unicode - now widely adopted - has massively expanded the amount of data held in the databases underpinning many customers' SAP systems, increasing their size of systems.
And the increasing bulk and complexity is causing worries about system failures following in the wake of potential upgrades, according to a recently released survey by SAP partner Macro4.
Almost all - 90 per cent - of SAP's customers in the UK, France, and Spain are now facing upgrade challenges thanks to the increased size of their databases, the Micro4 poll of 135 customers said. Organizations are looking at longer upgrades and increased complexity - 73 and 60 per cent respectively.
There's a fear among 41 per cent that these big and complex systems could lead to system failures following an upgrade, with 39 per cent concerned about losing their data.
A large percentage of the data in question, 67 per cent, is not even important to day-to-day business operations, according to Macro4. It's static or historical information.
Macro4, which specializes in document management for SAP systems, said the problem effects customers moving to SAP 6.0 - which implements Unicode and was introduced in 2005 - and off of versions 4.6 and 4.7. Macro4 recommends archiving before upgrading.
Companies are only now facing up to the size of their databases because many are still running 4.6 or 4.7, which are due to be end-of-lifed by the end of December this year and in 2012 respectively. Typically, upgrades can take up to twelve months while new implementations of SAP take years to complete.
Macro4 SAP product specialist Markus Fehr told The Reg that Unicode requires four bytes of memory per character, leading to a growth in the size of an SAP database or SQL Server from Microsoft running an SAP system of between 30 and 60 per cent. He said SAP's rival Oracle had done a bit better in managing the increase in data growth when it adopted Unicode.
Oracle, meanwhile, has tossed out a minor pricing concession to keep its customers from turning on it in the way SAP's customers recently turned.
The giant Monday said it has waived the first year of extended support fees for Oracle E-Business Suite Release 11i 10 until November 2011, JD Edwards EnterpriseOne 8.11 until December 2010, Siebel CRM 7.8 until May 2011, and Oracle Database 10g R2 until July 2011. Oracle's extended support for PeopleSoft Enterprise 8.9 has been waved until June 2011.
Oracle offers three types of support: premium, which last five years and covers database, application and middleware maintenance and upgrades; extended, which adds another three years on to premium; and sustaining, which provides help through call centers and knowledge bases.
The company said in a statement the move would help customers reduce the total cost of ownership of their Oracle systems. It is unclear how many customers will be affected by the change, or how much they will save.
The change comes after SAP customers reacted against SAP's increase in support costs just as IT budgets were being cut. Long-running, European customers - particularly in Germany - have become concerned that SAP 's becoming more like Oracle by pushing up prices to make a profit. ®
COMMENTS
SAP following the MS strategy of ever increasing hardware requirements?
Bloat the software and force a hardware upgrade. Make $en$e to me.
Clarification on the impact of Unicode encoding for SAP upgrades
Unicode can involve using up to 4 bytes for some characters, depending on the encoding scheme used. For SAP systems the encoding scheme in the database varies from vendor to vendor. For example, Oracle uses CESU-8 and MS SQL Server uses UTF-16.
The key issue with upgrades to ERP 6.0 however is that all data in the database needs to be converted to Unicode - and this means additional downtime for the SAP system. Therefore a data archiving strategy is best implemented before an upgrade as it will reduce the overall volume of data and hence the costly conversion time.
The fact that the database can be larger after the upgrade because of the Unicode encoding can lead to additional data management problems. Again data archiving could help here by reducing volumes.
Aside from the Unicode issue, we are finding that SAP users generally can make their upgrade process easier by using archiving to reduce the size of their database.
UTF-16
"Macro4 SAP product specialist Markus Fehr told The Reg that Unicode requires four bytes of memory per character" ... which as a sound bite is technically correct re. UTF-32
Trouble is, SAP uses UTF-16 on the application server layer and either UTF-8, CESU-8, or UTF-16 on the database layer.
Perhaps the 'SAP product Specialist'' should read SAP's FAQs
IT infrastructure monitoring strategies
Requirements Checklist for Choosing a Cloud Backup and Recovery Service Provider
Data control in the cloud
Cloud based data management
Enabling efficient data center monitoring
