On 2 May 2013 16:04, John Campbell <[email protected]> wrote:
> Unless the DataBase engine makes an effort to handle all > non-internal-code numbers in an interchangable format-- and with > appropriately fixed sizes-- the binary form of the data file-- or > container files, for a database-- will be incompatible if copied, bit > for bit, from one machine architecture to another... but there is a > performance impact to ensuring that all binary coded numeric fields > have, across all architectures, a consistent and "machine independant" > format. > Having the database swap the bytes on the fly for everything would be pretty expensive, and probably best done on database load only. And I would assume similar issues for floating point numbers that are kept in machine format (like when you go from DB2 on z/OS to DB2 on zLinux). Another area potentially is code page for character data. While the database may be able to translate the retrieved data based on table code page and application needs, I recall that we made some CPU usage improvements by doing that at the database load and keeping the tables in the native code page. Rob ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
