Access disk-storage information
| Disk-storage information | Description | LO-specification accessor function |
|---|---|---|
| Estimated number of bytes | An estimate of the final size, in bytes, of the
smart large object The smart-large-object optimizer uses this value to determine the extents in which to store the smart large object. This value provides optimization information. If the value is grossly incorrect, it does not cause incorrect behavior. However, it does mean that the optimizer might not necessarily choose optimal extent sizes for the smart large object. By default, this value is -1, which tells the smart-large-object optimizer to calculate the extent size from a set of heuristics. |
mi_lo_specget_estbytes() mi_lo_specset_estbytes() |
| Maximum number of bytes | The maximum size, in bytes, for the smart large
object The smart-large-object optimizer does not allow the smart large object to grow beyond this size. By default, this value is -1, which tells the smart-large-object optimizer that there is no preset maximum size. |
mi_lo_specget_maxbytes() mi_lo_specset_maxbytes() |
| Allocation extent size | The allocation extent size, in KB It is the size of the page extents for the smart large object. By default, this value is -1, which tells the smart-large-object optimizer to obtain the allocation extent size from the storage-characteristics hierarchy. |
mi_lo_specget_extsz() mi_lo_specset_extsz() |
| Name of the sbspace | The name of the sbspace that contains the smart
large object The sbspace name can be at most 18 characters long and must be null terminated. By default, this value is null, which tells the smart-large-object optimizer to obtain the sbspace name from the storage-characteristics hierarchy. |
mi_lo_specget_sbspace() mi_lo_specset_sbspace() |
For most applications, use the values for the disk-storage information that the smart-large-object optimizer determines. If you know the size of the smart large object, it is recommended that you specify this size in the mi_lo_specset_estbytes() function instead of in the onspaces utility or the CREATE TABLE or the ALTER TABLE statement. This mi_lo_specset_estbytes() function (and the corresponding Informix® ESQL/C ifx_lo_specset_estbytes() function) is the best way to set the extent size because the database server can allocate the entire smart large object as one extent.