Help get this topic noticed by sharing it on Twitter, Facebook, or email.

SF Objects Indexing in SQL

I have a question dealing with SF_Refresh/Replicate runs and its affect on indexing we have on our SalesForce objects in SQL. We created indexes on our Account table in SQL, there was a schema change, replication ran and the indexes were dropped. How can we keep indexes on refreshed tables in SQL?
1 person has
this question
  • If you have other indexes on the table (i.e besides the primary key on id), then you must recreate those indexes after running a sf_replicate.

    SF_Refresh does not remove the indexes so should not be a problem.  The exception is when there is a schema change and the sf_refresh turns into a sf_replicate.

    You could create your own "wrapper" stored procs that do the sf_replicate and then rebuild those additional indexes.
  • (some HTML allowed)
    How does this make you feel?
    Add Image

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned