Mobile Client Index Migration 
Purpose
The Mobile Client Index Manager maintains index information associated with the tables in the user database. However, to maintain information about the indexes, you need to upload the indexes to the mobile client index repository in the CRM server. This repository contains information about the indexes associated with the tables in the user database (IDES). The migration tool allows you to upload the indexes, defined on the tables in the user database, to the mobile client index repository in the CRM server.
The migration of the indexes from the mobile client to the CRM server is a one-time operation.
Implementation considerations
When you migrate indexes from the mobile client to the CRM server, you must consider the following:
· System (SAP or Customer)
If the system is SAP, this tool uploads the indexes to the SAP Index tables in the CRM server. However, in a customer system, the tool uploads the indexes to the Customer Index tables.
The mobile client index repository comprises of SAP Index tables and Customer Index tables. The SAP Index tables contain information about the indexes provided by SAP and Customer Index tables contain information about the indexes created or modified by the customer.
During migration in a customer system, if both SAP and customer have created an index with the same name on the same table in the user database, the index created by the customer is uploaded to the CRM server in an inconsistent state.
· Availability of index
This tool checks for the availability of an index based only on the name of the index.
· Unique index
The mobile client index manager does not allow you to define a unique index on a table. Therefore, when you upload a unique index to the CRM server, the state of the index is inconsistent.
· Clustered index
You can create only one clustered index on a table by using the Mobile Client Index Manager. Therefore, when you upload a clustered index to the CRM server, the state of the index is inconsistent.
· Mobile client index repository configuration settings
During migration, if any of the indexes violate the configuration settings, the same are uploaded to the CRM server. However, these indexes are disabled in the CRM server. The migration tool generates a migration log that contains information about the indexes that violated the configuration settings.
Integration
If the state of an index, uploaded to the CRM server, is inconsistent, you need to resolve the inconsistency by using the Mobile Client Index Manager.
See also: