SYSSBSPACENAME

onconfig.std value

None

if not present

0

range of values

Up to 128 characters. SYSSBSPACENAME must be unique, begin with a letter or underscore, and contain only digits, letters, underscores, or $ characters.

takes effect

When disk is initialized (destroys all data)

utilities

onspaces

refer to

The following material:

• Create an Sbspace or Temporary Sbspace
• Sbspace Structure
• Updating statistics, in the chapter on individual query performance in your IBM Informix Performance Guide
• Sbspace characteristics, in the chapter on configuration effects on I/O in your IBM Informix Performance Guide
• Writing user-defined statistics, in the performance chapter in IBM Informix User-Defined Routines and Data Types Developer's Guide
• Providing statistics data for a column, in the IBM Informix DataBlade API Programmer's Guide
• SBSPACENAME (specifies the name of the default sbspace)

SYSSBSPACENAME specifies the name of the sbspace in which the database server stores statistics that the UPDATE STATISTICS statement collects for certain user-defined data types. Normally, the database server stores statistics in the sysdistrib system catalog table.

Because the data distributions for user-defined data types can be large, you have the option to store them in an sbspace instead of in the sysdistrib system catalog table. If you store the data distributions in an sbspace, use DataBlade API or ESQL/C functions to examine the statistics.

Even though you specify an sbspace with the SYSSBSPACENAME parameter, you must create the sbspace with the -c -S option of the onspaces utility before you can use it. The database server validates the name of this sbspace when one of the following occurs:

• The database server attempts to write data distributions of the multirepresentational type to SYSSBSPACENAME when it executes the UPDATE STATISTICS statement with the MEDIUM or HIGH keywords.
• The database server attempts to delete data distributions of the multirepresentational type to SYSSBSPACENAME when it executes the UPDATE STATISTICS statement with the DROP DISTRIBUTIONS keywords.

Although you can store smart large objects in the sbspace specified in SYSSBSPACENAME, keeping the distribution statistics and smart large objects in separate sbspaces is recommended because:

• You avoid disk contention when queries are accessing smart large objects and the optimizer is using the distributions to determine a query plan.
• Disk space takes longer to fill up when each sbspace is used for a different purpose.