Did this article resolve your question/issue?



How to calculate the most appropriate value for -Bt

« Go Back


TitleHow to calculate the most appropriate value for -Bt
URL NameP109010
Article Number000149408
EnvironmentProduct: Progress
Version: 8.x, 9.x
Product: OpenEdge
Version: 10.x, 11.x
OS: All supported platforms
Question/Problem Description
How to calculate the most appropriate value for -Bt
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
When working with temp-tables it is best to keep as much in memory as possible.

The -Bt is used to allocate memory for Buffers for Temp-Tables.
The minimum value for -Bt is 10.
The default value prior to OpenEdge 10.1A was 10.  In OpenEdge 10.1A and later the default is 255.

The following algorithm is a simplistic version of what is done in the client code.  

A good basic method to calculate a close value for -Bt during the development phase:
<# of temp-tables in use at one time> * 9

If the application has 10 temp tables defined but only 5 are active at any one time then the following would a good setting for -Bt.
-Bt = 5 * 9


An alternate method typically used after deployment,  especially useful if access to the source code is not possible, is to monitor the size of the DBI file created by the client.

The formula for this method would be:
DBI size (in KB) * 1024 / -tmpbsize (1 for 1024 or 8 for 8192) = new value for -Bt.


In OpenEdge 10.1B the default tmpbsize was increased from 1K to 4K.
Last Modified Date10/27/2016 7:44 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.