Discontinued Indexes

JOIN, LD, FP(1), FP(2), and FP(3) indexes are not supported in SAP Sybase IQ 16.0.

Discontinued Item	Description
JOIN Indexes	SAP Sybase IQ no longer supports `JOIN` indexes. All references to this item have been removed from the documentation. Customers who are migrating a database from a previous edition must drop all `JOIN` indexes before upgrading to SAP Sybase IQ 16.0.
LD Indexes	`LD` (LOWDISK) indexes were replaced by `HG` indexes in release 12.0. If you have a very old database, note that SAP Sybase IQ no longer supports `LD` indexes. All references to this item have been removed from the documentation. Customers who are migrating a database from a previous edition must drop all `LD` indexes before upgrading to SAP Sybase IQ 16.0.
FP(1), FP(2), FP(3) indexes	SAP Sybase IQ no longer supports `FP(1)`, `FP(2)`, `FP(3)` indexes. Continuous `NBit` dictionary compression replaces 1, 2, 3 byte dictionary compression. `FP(1)`, `FP(2)`, `FP(3)` indexes rollover to `NBit` 8, 16, 24 respectively.

Discontinued Item

Description

JOIN Indexes

SAP Sybase IQ no longer supports JOIN indexes. All references to this item have been removed from the documentation.

Customers who are migrating a database from a previous edition must drop all JOIN indexes before upgrading to SAP Sybase IQ 16.0.

LD Indexes

LD (LOWDISK) indexes were replaced by HG indexes in release 12.0. If you have a very old database, note that SAP Sybase IQ no longer supports LD indexes. All references to this item have been removed from the documentation.

Customers who are migrating a database from a previous edition must drop all LD indexes before upgrading to SAP Sybase IQ 16.0.

FP(1), FP(2), FP(3) indexes

SAP Sybase IQ no longer supports FP(1), FP(2), FP(3) indexes.

Continuous NBit dictionary compression replaces 1, 2, 3 byte dictionary compression. FP(1), FP(2), FP(3) indexes rollover to NBit 8, 16, 24 respectively.

Note: Failing to drop all LD or JOIN indexes before an ALTER DATABASE UPGRADE in SAP Sybase IQ 16.0 causes the upgrade to fail, and the server will return a message that indicates that a database upgrade is not possible when these objects are in use.

To recover, shutdown the 16.0 server, open the database with SAP Sybase IQ 15.x, and drop all LD and all JOIN indexes before proceeding with the migration.