• So why bother making replication able to replicate schema then? There is only one schema change that replication cannot handle -- dropping tables that are part of a publication. Why would Microsoft program CRM to drop tables to add a column? Why would you ever want to do that? Ignore exceptions (that in my opinion are bad form anyway) -- what possible reason is there for a professional product to drop a table whenever you want to add a column? That's the core of my rant.