Re: [sap-basis] Difference between Single code page & MDMP
Posted by
Admin at
|
Share this post:
|
|
0 Comments
 | Posted by Nic Harvard (Principal Consultant) on Aug 11 at 6:12 PM |  Mark as helpful |
Akk!!
Lars, your replies are usually spot-on, but thats a huge
recommendation for disaster.
Really huge.
Forget transactional data corruption - you could get serious
mater-data screw-ups if you do that.
MDMP>unicode, you need to go through a huge mapping excercise. It is
not rocket science, but it ain't trivial from a workload point of
view...
2009/8/11 Lars-Erik Hallsten via sap-basis <sap-basis@groups.ittoolbox.com>:
> Posted by Lars-Erik Hallsten (CEO & Senior Consultant)
> on Aug 11 at 5:28 PM
> Mark as helpful
> Hi,
>
> The migration from MDMP to unicode is not that messy. Just export the
> database with only one codepage, then install it into a single codepage
> system, then perform a normal unicode conversion.
>
> Regards,
> LEH
>
>
> From: Nic Harvard via sap-basis [mailto:sap-basis@Groups.ITtoolbox.com]
> Sent: 11. august 2009 22:41
> To: Lars-Erik Hallsten
> Subject: RE:[sap-basis] Difference between Single code page & MDMP
>
>
>
>
> Posted by Nic Harvard (Principal
> Consultant)
> on Aug 11 at 4:42 PM
> <http://it.toolbox.com/api/ContentVote/2926616/1/1/> Mark this reply as
> helpfulMark as helpful
> Also, if you ever implemented MDMP, your upgrade to unicode is going to be a
> whole bunch more painful.:(
> Single code page is basically "one language" - or at least, one alphabeti
> spagetti set - western EU or similar.
> MDMP was a "bubblegum and duct-tape" solution before SAP went unicode, and
> like all such, tends to make your life harder in the long run.
> Unicode is the way you want to go - the main overheads are in DB space,
> which is cheap - because it need to use double-byte per character, to
> accomodate potential katakana (eg) characters or similar.
> If you really want to research this, you will be dumbstruck by the number of
> different alphabets and scripts used today in the real world. And thank your
> lucky stars SAP has not been around long enough to translate from ancient
> minoan, nor does it support chinese ideographic translation yet:)
__.____._ Lars, your replies are usually spot-on, but thats a huge
recommendation for disaster.
Really huge.
Forget transactional data corruption - you could get serious
mater-data screw-ups if you do that.
MDMP>unicode, you need to go through a huge mapping excercise. It is
not rocket science, but it ain't trivial from a workload point of
view...
2009/8/11 Lars-Erik Hallsten via sap-basis <sap-basis@groups.ittoolbox.com>:
> Posted by Lars-Erik Hallsten (CEO & Senior Consultant)
> on Aug 11 at 5:28 PM
> Mark as helpful
> Hi,
>
> The migration from MDMP to unicode is not that messy. Just export the
> database with only one codepage, then install it into a single codepage
> system, then perform a normal unicode conversion.
>
> Regards,
> LEH
>
>
> From: Nic Harvard via sap-basis [mailto:sap-basis@Groups.ITtoolbox.com]
> Sent: 11. august 2009 22:41
> To: Lars-Erik Hallsten
> Subject: RE:[sap-basis] Difference between Single code page & MDMP
>
>
>
>
> Posted by Nic Harvard (Principal
> Consultant)
> on Aug 11 at 4:42 PM
> <http://it.toolbox.com/api/ContentVote/2926616/1/1/> Mark this reply as
> helpfulMark as helpful
> Also, if you ever implemented MDMP, your upgrade to unicode is going to be a
> whole bunch more painful.:(
> Single code page is basically "one language" - or at least, one alphabeti
> spagetti set - western EU or similar.
> MDMP was a "bubblegum and duct-tape" solution before SAP went unicode, and
> like all such, tends to make your life harder in the long run.
> Unicode is the way you want to go - the main overheads are in DB space,
> which is cheap - because it need to use double-byte per character, to
> accomodate potential katakana (eg) characters or similar.
> If you really want to research this, you will be dumbstruck by the number of
> different alphabets and scripts used today in the real world. And thank your
> lucky stars SAP has not been around long enough to translate from ancient
> minoan, nor does it support chinese ideographic translation yet:)
Copyright © 2009 CEB Toolbox, Inc. and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
In the Spotlight
How Can Predictive Analytics Drive Competitive Advantage? Find out here
View this thread online
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
