Posted on 2011-03-16
" If you change schema options after a publication is created, you must generate a new snapshot."
Is there any workaround for this if it's merge application? To elaborate, we are having merge replications for a database which's about 5 GB. With in an year or so, the size of the database is expected to grow by a huge margin.
Since the size of the database is relatively small, my boss is ok with regenerating a snapshot on the subscriber if there are any schema changes made on the publisher. But he's totally against generating a new snapshot for any schema changes made in the near future (as we are planning to implement merge application for various other application databases, so they want to setup company wide standards for similar tasks) , so he's asking me to give an alternate solution for this. Can you guys give me some input into this, your response is truly appreciated.
FYI, the version of the database in question is SQL Server 2008 R2 enterprise on Windows 2008 R2 enterprise