Question : SQL Server Replication Question

Hi Experts,

I am working on setting up Transactional Replication from SQL Server 2005 Ent Edition to SQL Server 2008 Ent Edition.

What are all the situations when Replication has to be disabled/ stopped when a production update is being done. What are the possibilities of the update script breaking because the ... TABLE IS BEING PUBLISHED.

To my knowledge, few of them are:

1) Altering a primary key is disallowed and results in an error.
2) Adding an Identity column to a table being replicated, Altering and dropping identity columns that are managed by replication are not supported.

Please let me know all the possible issues so that I can make my application team aware of them.

Thanks,

Answer : SQL Server Replication Question

Yes, if the table is published for replication you can not:

- rename it
- drop and recreate it
- change the primary key
- alter/drop identity columns
- rename columns
- truncate its content

But you can:

- add/drop column (except PK)
- add/drop index (except PK index)
- add/drop constraint

So inspect that script and find all of ALTER, CREATE or DROP belong to this table and filter the sensitive statements.