ID: Q131910
A scheduled table refresh that uses the option to Truncate the table as well as create the index may fail to work because the index already exists on the target table.
Do not enable the Index Rebuild option when you choose the Truncate Table option. You can also modify the table creation script so that it does an existence check for the index as it does for the actual table using the EXEC command.
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
When you enable a scheduled refresh of a table to use the Truncate option, the option to rebuild the index remains even though it really only applies to the Drop Table option for scheduled table refresh. When the Distribution process goes to recreate the index after the table creation, the index already exists, and the Distribution process fails with an ODBC error.
Additional query words: sql6 enterprise manager replication
Keywords : kbprg SSrvProg kbbug6.00 SSrvWinNT
Version : 6.0
Platform : WINDOWSLast Reviewed: May 1, 1997