Skip to main content
Database Administrators

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 1
    Just a theory but perhaps there were unreplicated commands with the original partition definition that had not yet been applied to the subscriber when the subscriber partitioning was changed. I think you need to suspend updates on replicated data before making the partition changes to the publisher and subscriber. Commented Apr 6, 2016 at 12:28
  • That's a good thought. I'm blanking right now, but is there an easy way to sort of fit that in between the replication actions that are taking place on the subscriber? Commented Apr 6, 2016 at 12:39