You create a subscriber in SQL Server Compact 3.5 Service Pack 2 (SP2), and then synchronize the subscriber with a publisher that is in SQL Server.
You create an index that contains a multicolumn index that has a defined sort order for an article of the publication. For example, you create the index by using the following statement:
CREATE INDEX index_name on table_name ([Column1] ASC, [Column2] DESC)
In this scenario, the sort order of the second column is incorrect after the index creation statement in the .out file is sent during synchronization. Additionally, after SQL Server Compact 3.5 downloads the snapshot during initialization of the replication process, the database table of the subscriber does not specify an index sort order in the INFORMATION.SCHEMA.INDEXES view.
The hotfix that resolves this issue is included in cumulative update package 7 for SQL Server Compact 3.5 SP2.
For more information about how to obtain cumulative update package 7 for SQL Server Compact 3.5 SP2, click the following article number to view the article in the Microsoft Knowledge Base:
2553608 Cumulative Update 7 for SQL Server Compact 3.5 Service Pack 2
To work around this issue, manually create an index with a defined sort order on the subscriber database after the data is downloaded from the publisher.
For more information about the CREATE TABLE statement, visit the following MSDN website: