Table 9-1 describes the new limits for index size for APL and DOL tables:
Page size |
User-visible index row-size limit |
Internal index row-size limit |
|---|---|---|
2K (2048 bytes) |
600 |
650 |
4K (4096bytes) |
1250 |
1310 |
8K (8192 bytes) |
2600 |
2670 |
16K (16384 bytes) |
5300 |
5390 |
Because you can create tables with columns wider than the limit for the index key, these columns become non-indexable. For example, if you perform the following on a 2K page server, then try to create an index on c3, the command fails and Adaptive Server issues an error message because column c3 is larger than the index row-size limit (600 bytes).
create table t1 (c1 intc2 intc3 char(700))
“Non-indexable” does not mean that you cannot use these columns in search clauses. Even though a column is non-indexable (as in c3, above), you can still create statistics for it. Also, if you include the column in a where clause, it will be evaluated during optimization.
