Writing to temporary files creates i/O activity to DBI files that can slow down client performance. The amount of temporary file I/O activity varies dependent on the application being used. In OpenEdge 10.1x there have been a couple of changes associated with the client temporary files, specifically Temp tables which are stored in the clients .dbi file. These changes have resulted in the files being larger than they were in Progress 9.
Summary of OpenEdge 10.1 changes for temp-tables:Number of Buffers for Temporary Tables -Bt
- The -Bt parameter is used to identify the number of buffers in the temporary table database pool (akin to -B for database shared memory).
- In OpenEdge 10.1A the default -Bt changed from 10 to 255.
Temporary Table Block size -tmpbsize
- The temp-table database block size dictates the size of each buffer in the temp-table database buffer pool for the current OpenEdge Session (akin to the database blocksize).
- -tmpbsize was first introduced in Progress 9.1D07 where the default is 1KB
- In OpenEdge 10.1B, the default -tmpbsize changed from 1KB to 4KB.
Refer to Article
How does -Bt work with Temp-Tables? Type II Storage AreasIn
OpenEdge 10, the temporary file database (DBI) uses a Type II Storage Areas instead of a Type I Storage Area (block by block allocation) in Progress 9. Type II storage areas are comprised of clusters. A cluster is a contiguous allocation of space for one type of database object. Depending upon the number of temporary files being used by the application, the DBI file could be much larger.
Refer to Article
What are the maximum number of records that can be stored in a TEMP-TABLE? 
