Enterprise Edition Home | Express Edition Home | Previous Page | Next Page   Table Performance Considerations > Managing Sbspaces >

Changing Storage Characteristics of Smart Large Objects

When you create an sbspace but do not specify values in the -Df option of the onspaces -c -S command, you use the defaults for the storage characteristics and attributes (such as logging and buffering).

After you monitor sbspaces, you might want to change the storage characteristics, logging status, lock mode, or other attributes for new smart large objects.

The database administrator or programmer can use the following methods to override these default values for storage characteristics and attributes:

Table 6 summarizes the ways to alter the storage characteristics for a smart large object.

Table 6. Altering Storage Characteristics and Other Attributes of an Sbspace
Storage
Character-istic or Attribute
System Default
Value
System-Specified Storage Characteristics Specified by
-Df Option in
onspaces Utility
Column-Level
Storage
Characteristics Specified by
PUT clause of
CREATE TABLE or
ALTER TABLE

Storage Characteris-tics Specified by a DataBlade API Function
Storage Characteris-tics Specified by an ESQL/C
Function
Last-access time OFF ACCESSTIME KEEP ACCESS TIME, NO KEEP ACCESS TIME Yes Yes
Lock mode BLOB LOCK_MODE No Yes Yes
Logging status OFF LOGGING LOG, NO LOG Yes Yes
Size of extent None EXTENT_SIZE EXTENT SIZE Yes Yes
Size of next extent None NEXT_SIZE No No No
Minimum extent size 2 kilobytes on Windows
4 kilobytes on UNIX
MIN_EXT_SIZE No No No
Size of smart large object 8 kilobytes Average size of all smart large objects in sbspace: AVG_LO_SIZE No Estimated size of a particular smart large object Maximum size of a particular smart large object Estimated size of a particular smart large object Maximum size of a particular smart large object
Buffer pool usage ON BUFFERING No LO_BUFFER and LO_ NOBUFFER flags LO_BUFFER and LO_ NOBUFFER flags
Name of sbspace SBSPACE-NAME Not in -Df option. Name specified in onspaces -S option. Name of an existing sbspace in which a smart large object resides: PUT ... IN clause Yes Yes
Fragmenta-tion across multiple sbspaces None No Round-robin distribution scheme: PUT ... IN clause Round-robin or expression-based distribution scheme Round-robin or expression-based distribution scheme
Last-access time OFF ACCESSTIME KEEP ACCESS TIME, NO KEEP ACCESS TIME Yes Yes
Lock mode BLOB LOCK_MODE No Yes Yes
Logging status OFF LOGGING LOG, NO LOG Yes Yes
Size of extent None EXTENT_SIZE EXTENT SIZE Yes Yes
Size of next extent None NEXT_SIZE No No No
Minimum extent size 2 kilobytes on Windows
4 kilobytes on UNIX
MIN_EXT_SIZE No No No
Size of smart large object 8 kilobytes Average size of all smart large objects in sbspace: AVG_LO_SIZE No Estimated size of a particular smart large object Maximum size of a particular smart large object Estimated size of a particular smart large object Maximum size of a particular smart large object
Buffer pool usage ON BUFFERING No LO_BUFFER and LO_ NOBUFFER flags LO_BUFFER and LO_ NOBUFFER flags
Name of sbspace SBSPACE-NAME Not in -Df option. Name specified in onspaces -S option. Name of an existing sbspace in which a smart large object resides: PUT ... IN clause Yes Yes
Fragmenta-tion across multiple sbspaces None No Round-robin distribution scheme: PUT ... IN clause Round-robin or expression-based distribution scheme Round-robin or expression-based distribution scheme

Altering Smart-Large-Object Columns

When you create a table, you have the following options for choosing storage characteristics and other attributes (such as logging status, buffering, and lock mode) for specific smart-large-object columns:

Later, you can use the PUT clause of the ALTER TABLE statement to change the optional storage characteristics of these columns. Table 6 shows which characteristics and attributes you can change.

You can use the PUT clause of the ALTER TABLE statement to perform the following actions:

For example, the BLOB data in the catalog table in the superstores_demo database is stored in s9_sbspc with logging turned off and has an extent size of 100 kilobytes. You can use the PUT clause of the ALTER TABLE statement to turn on logging and store new smart large objects in a different sbspace. For information about sbspace logging, see smart large objects in the logging chapter of your IBM Informix: Dynamic Server Administrator's Guide.

For information about changing sbspace extents with the CREATE TABLE statement, see Extent Sizes for Smart Large Objects in Sbspaces.

For more information about CREATE TABLE and ALTER TABLE, see the IBM Informix: Guide to SQL Syntax.

Enterprise Edition Home | Express Edition Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]