Kbase 17280: Work-file vs. Temp-file: where they're used and why
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Work-file vs. Temp-file: where they're used and why
DRAFT COPY - Currently under review and edit.
INTRODUCTION:
=============
This Progress Technical Support Knowledgebase entry is intended to
explain which versions of PROGRESS use work tables (v6 and before),
which versions of PROGRESS us temp-tables (v7 and beyond), where they
are stored, and how they are used.
WHY YOU NEED TO KNOW THIS:
===========================
Work-files are stored only in memory, in space sized by the -l
parameter. When you run out of space, you get an error.
Work-files do not have indexes.
On the other hand,
Temp-tables are stored in the client-side structure that resembles a
miniature single-user temporary database. This "database" has no .bi
file and no schema. The schemata of temporary tables are defined in
the application by 4gl declarations.
Temp-tables are buffered in memory but spill over to disk when the
buffers fill up. -Bt determines how many blocks are buffered in
memory by the client.
Temp-tables have indexes.
NOTE: There are known issues with OS/2 clients that have not been
resolved as of this writing.
MEM 9/97
Progress Software Technical Support Note # 17280