Binding is the copying of the definition of a table, screen, or rule, or the data of a table into the shared storage of an Execution Environment when the first access is made to it within a session. Subsequent references within the session access this copy.
Binding can significantly reduce I/O between the Execution Environment and the Data Object Broker, therefore optimizing access to the database. If binding is not in place, upon each subsequent reference to a table, screen or rule, a new copy is brought back into storage from the data store.
The use of the bound copy is in effect for the life of the session. If a parameterized table is bound, only the table instances that have been referenced are brought into the shared storage, even though the bind is on the whole table.
In addition to bound storage limits in the Execution Environment, each bound table has a storage limit of 26.5 KB. This does not include additional storage required for indexing. The limit represents the sum of sizes of all occurrences retrieved by the Data Object Broker. The size of additional storage is
(number of occurrences) x (keysize + 4).
TIBCO Object Service Broker Parameters for more information about the REGIONTABLESIZE Execution Environment parameters.