Due to the design of indexes within a data server, which provides an optimum search path, index rows are ordered for fast access to the table’s data row. Index rows which contain row identifiers (RIDs), are treated as binary to achieve a fast access to the user table.
Within the same architecture platform, the order of index rows remains valid and search order for a selection criteria takes its normal path. However, when index rows are translated across different architectures, the order which optimization was done is invalidated. This results in an invalid index on user tables when a cross-platform dump and load feature is executed.
To fix indexes on the target system after load from a different architecture dump, you can use one of two methods:
Drop and re-create all of the indexes.
Use sp_post_xpload.
Since the data point and information varies from usage on indexes, the schema, user data, number of indexes, index-key length, and number of index rows, in general, it requires planning to re-create indexes on large tables, as it can be a lengthy process. sp_post_xpload validates indexes, drops invalid indexes, and re-creates dropped indexes in a single command.
Since sp_post_xpload performs many operations, it may take longer than dropping and recreating indexes. Sybase recommends that you use drop and re-create indexes on databases larger than 10G.
