Would there be an issue creating an index on replicated table?
I have a query that is very slow when joining on a view which is based on a replicated table. Execution plan recommends a clustered index on the replicated table.
Would there be an issue creating an index on replicated table?
There should be no issue with additional index on the target table of replicate task. You would need to set the task to truncate table on full load opposed to drop and create to maintain the index if you ever need to do a reload.
Indexes consume disk space and you need to check the storage limit. please check with your DBA's before creating index so that they can analyze further to see if there are any other ways before adding indexes.
