replication setup
-
i am currently planning to setup transactional replciation of some articles from sever A to Server B. We have another server C to which we have to replicate this data from Server B. We can't move data from Server A to Server C. I would like to setup replication between Server B and Server C. I tested it and it works. But I am skeptical whether it works as expected when pushed to production environment. Any suggestions?
-
What specifically are you skeptical about? You question is a bit vague
-
arnipetursson (12/16/2014)
What specifically are you skeptical about? You question is a bit vagueWhat i was trying to do is a table part of replication reaching from Server A to Server B will also be part of replication from Server B to Server C. So the data flows from Server A to Server C via Server B.
-
Basically your database on Server B is both a Subscriber and Publisher database? Is that what you mean? This should be fine albeit a bit funny to get your head around esp. in a disaster scenario...obviously you will need to snapshot twice to get the data from A to C (as you will have a publication on Server A and a publication on Server B)
-
I don't like supporting these daisy chaining scenarios but I agree, it should work just fine.
I don't consider it good repl design though because if something happens to the 1st subr you have to reinit both of them, including setting up a new publ on the orig subr. And if your DB is big then there goes the next couple days of your life.
Watch my free SQL Server Tutorials at:
http://MidnightDBA.com
Blog Author of:
DBA Rant – http://www.MidnightDBA.com/DBARantMinion Maintenance is FREE:
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply