Guys, I have an very urgent support request in my organization. And im new to Replication, but at least learned some during the setup, and worked on it for past months facing every kind of difficulties, Google search helped much, but after dozens try, I'm stuck here with one issue/question: [b]Can a subscriber DB to other server to be the publisher DB in a new merge replication. [/b]If my statement is hard to understand, here's background.We have Server A, B, C is running SQL 2005 which we need to retire them all.Server A is a publisher setup merge replication with B & C respectively.Now we setup X, Y, Z running SQL 2014 to replace the A, B, C.Server X is a publisher setup merge replication with Y & Z respectively.As there's no downtime can be allowed, there're multiple applications relies on the DB, we need to move app pointers in some period of time. So, we need both environment work for a couple of weeks, to slowly migrate to X,Y,Z. Any changes happened on server A need to be sync to X, and X is also getting new data but no need to sync back to A.Because per MS, SQL 2005 to SQL 2014 beyond 2 version steps, replication may not work well may have unexpected result not suggested, so i have setup a interim server T running SQL 2008 R2 as broker to pass data between A & X, A -> T setup transactional replication and verified working fine, and server T pass data to X for transactional replication is fine. (Oh yeah!)as earlier said, X setup as publisher and merge with Y & Z, it is working as expected, verified if change occurred in X, it updated to Y & Z. (Oh yeah!!)BUT, the change happened from A, pushed to T, pushed to X, it is not reflected in Y & Z. only direct change happened on X can be reflected in Y & Z. UNBELIEVABLEI hope my description is clear enough for any suggestion. I hope someone has also gone through the same complicated setup.Any word would help.thanks,Jack
↧