Unicode System - Effects on SAP Server

Unicode influences the following factors:
=================================================
- Load of applications on hardware (CPU & RAM)
- Seehttp://service.sap.com/unicode
- Seehttp://service.sap.com/performance
- Result: about +30% to +35% CPU and +50% RAM
- Size of database
- See http://service.sap.com/unicode
- The result depends on the usage of UTF-8 (+36%) or UTF-16 (+60% to 70%).

Performance of the database
- Ask the database vendor for the performance results of databases
using Unicode.

Unicode systems use between 1 and 5 bytes of space to store single characters, based on the character and its Unicode representation. As a result, in a simple estimate, the resources of the system could be doubled to be prepared for worst-case scenario.

In reality, the load on the CPU caused by the applications, in this case, the SAP software, increased by about 30-35%. The load on the RAM, again caused by application software and not database software, increased by about 50%.

The size of the database of Unicode systems, compared to non-Unicode systems, depends largely on the type of Unicode representation chosen. UTF-16 (+60% to 70%) requires more space than UTF-8 (+36%).

The performance of the database system is also affected. For performance of data
on the database systems under Unicode, contact your database manufacturer.

To send POP UP to All in SAP - INSTANT POPUP

SEND POP UP TO ALL - INSTANT POPUP in SAP
==========================================

You could use function module TH_POPUP directly from transaction SE37,
or if you search the Web (google) for ZPOPUP or so, you would find some ABAP program examples that uses this FM....

How does an SAP Work Process access memory?

An SAP process accesses memory in the following way:
-------------------------------------------------------

• In dialog processes (Process type DIA)
1. The first section of the roll area up to parameter ztta/roll_first - then -
2. Extended memory up to parameter ztta/roll_extension -or- extended memory (size: em/initial_size_MB) is exhausted - then -
3. The rest of the roll area (size: ztta/roll_area) - then -
4. Process local memory up to parameter abap/heap_area_dia -or- operating system swap space is exhausted -or- the process's data segment size is exceeded -or- the process's address space is exceeded -or- the operating system's address space is exceeded.

NOTE: Under Windows NT the allocation sequence of non-dialog work processes is the same as with a dialog work process.

• In non-dialog Processes (Process type VB, UP, BTC)
1. The total roll area (size: ztta/roll_area) - then -
2. Process local memory up to parameter abap/heap_area_nondia -or- operating system swap space is exhausted -or- the process's data segment size is exceeded -or- the process's address space is exceeded -or- the operating system's address space is exceeded. - then -
3. Extended memory up to parameter ztta/roll_extension -or- extended memory (size: em/initial_size_MB) is exhausted.