title: SQL server bi-directional replication and auto-increment primary key
body: <p>I have read <a href="https://stackoverflow.com/questions/1924631/sql-server-merge-replication-primary-key-violations">here</a> that a simple way to manage auto-increment primary keys with (bi-directional) replication between two instances, is to have one server always be even numbers and the other number always odd.</p>
  
  <p>I understand that will cause problems if you have a clustered index on the primary key, epically if one server is used significantly more than the other.</p>
  
  <p>Is this correct? How can I prevent the table from getting too fragmented if server A is always used much more than server B?</p>
  
  <p>Can I use index padding to pad out my PK index to make sure that the table doesn't fragment but just takes up more disk space? What percentage should I be using? 50%?</p>