SQL Operations Guide

Default HUGE File Tables with FairCom DB SQL

HUGE files (c-tree files larger than four gigabytes) are frequently encountered with today’s massive storage needs. To accommodate these increased table sizes, FairCom DB SQL creates files as HUGE by default. (Prior to FairCom DB SQL V9, new tables were created as standard non-HUGE c-tree files.) An optional STORAGE_ATTRIBUTES clause containing 'HUGE' was available to create FairCom DB SQL HUGE tables.

Reversing the previous behavior, the STORAGE_ATTRIBUTES clause supports a NOT HUGE option to create standard size c-tree tables.

For backward compatibility, it is possible to revert to the original FairCom DB SQL behavior and set theFairCom DB SQL default to ‘NOT HUGE’ by adding the following configuration keyword to ctsrvr.cfg:

SQL_OPTION NO_HUGEFILE

The STORAGE_ATTRIBUTES clause will override any default configuration settings. Whether a table is created HUGE or NOT HUGE with respect to the ctsrvr.cfg configuration and the STORAGE_ATTRIBUTES statement clause is summarized in the following table:

FairCom DB SQL Configuration	No specific STORAGE_ATTRIBUTES	STORAGE_ATTRIBUTES “HUGE”	STORAGE_ATTRIBUTES “NOHUGE”
default ctsrvr.cfg	HUGE	HUGE	NOT HUGE
SQL_OPTION NO_HUGEFILE	NOT HUGE	HUGE	NOT HUGE

Example

CREATE TABLE table1 (column1 INT, column2 CHAR(10)) STORAGE_ATTRIBUTES 'NOHUGE'

CREATE TABLE table2 (column1 MONEY, column2 VARCHAR(20)) STORAGE_ATTRIBUTES 'HUGE'

To combine STORAGE_ATTRIBUTE options, separate them with a semicolon (;).

Note: HUGE file support is not available for the Windows CE version of FairCom DB SQL.