Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

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

Can you please advise how can I keep slave database up to date while it's in transactional replication with master.

I mean what If I change indexes, columns, tables or sthm else in master dabase? What should I do in this case?

Should I make this changes to both databases simultaneously or transactional article is enough to handle it?

share|improve this question
up vote 3 down vote accepted

By default, replication will push out the following DDL changes to subscribers:


And by default, I mean unless you have specified otherwise when you made a call to sp_addpublication when setting up the publication (even if done through the GUI, this is the underlying stored procedure that is called). There is a parameter for that stored procedure, @replicate_ddl, that is set to 1 by default, meaning that the above DDL commands will replicate to subscribers for the articles in the publication.

When you made your initial call to sp_addarticle, you would have specified (again, even if through the GUI where all the article options are set) which indexes (clustered and nonclustered) were generated for subscribers to create for initialization as well.

Reference :: How to: Replicate Schema Changes

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.