Kbase P119344: Will setting SQL Width to 32K result in padded 32K buffers pushed over the network regardless of the
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/10/2010 |
|
Status: Unverified
GOAL:
Will setting SQL Width to 32K result in padded 32K buffers pushed over the network regardless of the actual size of the data?
GOAL:
Does the SQL engine transfer data in sizes matching the actual size of the data or the SQL-WIDTH setting?
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
FIX:
Setting SQL Width to 32K will not result in padded 32K buffers pushed through the network regardless of the actual size of the data.
In OE 10.0B setting width to 32K may make sorting this very wide data more costly.
The value of SQL-WIDTH is used by the SQL engine to allocate a data buffer to hold the value of a column, when the column is selected by a SQL statement.
There can be costs in sorting (for the ORDER BY, or GROUP BY, or DISTINCT phrases) in our current sort implementation when the SQL-WIDTH is very large.
Our current sort allocates sort record space based on the defined size (== SQL-WIDTH) of a column. Very large column sizes consume much more sort space, and make sorting much more expensive.