Replication and Data Migrations

  • I have a test database and transactional replication set up and running properly. Now that it is up, I have a couple of questions concerning making changes to the Publication database. My understanding is that if I need to make changes to the table structures or add tables to the Publication database that I need to remove replication, make my changes, and then set-up replication again. Is this correct or can I just stop all the SQL Agent replication jobs, restart them after making the changes, and then reinitialize the subscription?

    Similarly, if I do a data migration that adds 30,000 rows to the base table and 25,000 + rows to 10+ other tables, should I remove replication before migrating? The process runs about 25 hours.

    I am using SQL 2008 R2 on a windows 2008 R2 server. All service packs have been applied.

    Thanks, Rosalind

  • Depending on how you configure your publication, replication is quite happy for you to make changes to table structures and replication will make the equivalent change to the subscriber. Have a look at article "Making Schema Changes on Publication Databases" in Books Online - it should tell you all that you need to know.

    As for the data migration - that it your call. 30,000 + 25,000 rows in 25 hours doesn't seem like very much to me - personally, I would leave replication running.

  • Thank you for your help. I will check out the article and do some more testing.

  • Check out this article, I think it will help 🙂

    http://www.sqlservercentral.com/Forums/Topic1388718-391-1.aspx#bm1388866

    ______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience

  • Thank you. The article was helpful. I like your problem solving process.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply