Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have two databases in same instance of SQL Server 2005, configured for Transactional replication. When data is changed, the changes are replicated properly in both databases. For the new created tables, the table is not created automatically in another replicated database. Even it does not allow changing the structure of exiting table. Can you please let me know how I can manage this issue? The changes in database objects are very regular in our system, which needs to be replicated frequently.

share|improve this question

Just as you had to add the tables to replication initially, so you have to add new tables to the existing publication. Replication is granular in nature. That is, you can choose to publish any subset of them while leaving replication blissfully unaware of the others. So, when you add a new table, you have to explicitly choose to add that table to any publications that you want it added to. I've found the easiest way to manage that is through calls to the sp_addarticle and sp_addsubscription stored procedures.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.