Be default, when you create log shipping, the secondary database is in read only mode. You are not allowed to create any additions to the tables. If you create a publication, on such a database, it will fail because it tries to create/update system tables, and add new tables regarding replications. (Yes it creates them in distribution database and in publication database)
So we came up with a different approach:
We decided not to create publications. We enabled replication on secondary server and on the day of transfer, we stopped all transactions and created replications manually.
More on this tomorrow:
Just a piece to monitor: The picture here shows the setting we need to select when setting up replication using management studio. The default is "drop existing object and create new one", but we need to select "keep existing object unchanged"
|Share this post :|