Kbase P89791: Why is an ascii dump file larger than the binary dumped file, when dumping the same table?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/08/2010 |
|
Status: Verified
GOAL:
Why is an ASCII dump file larger than a binary dumped file?
GOAL:
How come ASCII dump files and binary dump files for the same physical table are different sizes?
GOAL:
Why aren't dump files the same size for a table regardless of the dump method being used?
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
FIX:
Progress ASCII dump files are much larger than binary dump files. The difference in size is associated with spaces and double quotes, we add to fields when exporting data to an ASCII file.
Example:
A table 2.9 GB when dumped via binary dump produced a file which was 3 GB in size. The same table when exported using a 4GL routine, resulted in multiple files which when totaled equaled 5 GB.