Important DBSControl Parameter

DictionaryCacheSize: For the current default and maximum sizes of the dictionary cache,

NumStatisticsCacheSegs: You can use the DBS Control field NumStatisticsCacheSegs to change the
system-wide size of
the statistics cache. The default size of the cache is 4 segments of 1024 KB each, which makes
the default size of the cache 4 MB.

MaxRequestsSaved: When the request cache is initialized during Teradata Database start-up, the
number of cache entries is set to MaxRequestsSaved, a DBS Control field. The default value of
MaxRequestsSaved is 600 and the value can be modified within the range of 300 - 2000.
The total size of the request cache that can be saved is limited to 100 MB. This limit is checked
only if the number of request cache entries used is more than 300. If the number of request
cache entries in use is 300 or less, then 100 MB limit is not checked.

DisablePeekUsing:

You can control the availability of parameterized value peeking on your system by setting the
DisablePeekUsing performance field

FALSE: enabled for your system. This is the default.

TRUE: disabled for your system.

ObjectUseCountCollectRate:

When a specific user-defined time interval is reached.

You can specify a time-based flushing interval using the DBS Control field
ObjectUseCountCollectRate. Teradata Database flushes the OUC cache when either of the
following events first occurs.
• The specified elapsed time since the last flush of the cache is reached.
• The cache is full.

• DefaultPermSkewLimitPercent: Controls the skew factor on permanent space

• DefaultSpoolSkewLimitPercent: Controls the skew factor on spool space
• DefaultTempSkewLimitPercent: Controls the skew factor on temporary
Space.
GlobalSpaceSoftLimitPercent: The percentage by which a database or user is allowed to exceed the
maximum space limit. This setting applies to PERM, SPOOL, or TEMP space. The default
value is 0.

You can set data block sizes globally using these DBSControl fields:

PermDBAllocUnit,
PermDBSize, and
JournalDBSize.

These fields determine the maximum size of permanent data blocks that hold multiple rows.
(A row that exceeds the size of a multirow data block is put into a block of its own.)

MergeBlockRatio: As part of full-table modify operations, where the system sequentially scans the
table as part of the operation,
Teradata Database can merge small DBs into larger ones as the modifications are performed. While
this can
make some of the initial modifications to the table more expensive, it makes future full table
modifications
and queries cheaper by reducing the number of DBs in the table, which reduces disk I/Os.

FreeSpacePercent:

Global parameter that the system uses to determine the percentage of

space to leave unused on each cylinder during bulk loading operations
such as MultiLoad and FastLoad. This default can be overridden at the
table level with the FREESPACE clause.
Choose a percentage that reflects the net growth rate of your data tables
(INSERTs minus DELETEs). For example, most sites choose 5 to 15%.

OverflowMaxPermSpace-Percentage and OverflowMaxPermSpace-KByteCount:

If a space-intensive operation, such as a load utility or restoring from an archive, exceeds

available perm space, two DBS Control utility fields can be set temporarily to allow operations
to complete and avoid out of space errors. The settings apply to all operations and all
instances of space accounting, such as table inserts, so Teradata recommends setting these
fields to a non-zero value only temporarily