Hi,
I think this may be my first question on MS SQL DBA work, so I appreciate any constructive criticism to my post.
I am facing a restructuring of one of my site's setup to where two facilities that share a transactionally replicated server will be split, each to their own server. Due to limitations of the vendor software currently running on these, we face severe difficulty in actually separating their data before (or even after) we split them. So the project group's leanings have been towards duplicating the server, renaming etc., and having each facility run on their own instance.
This obviously presents great challenges for the transactional replication scenario. We normally run a snapshot of any new facility writing to the server functioning as the data warehouse and let the transactional replication run from there on. In this instance, we'd end up creating duplicates on the warehouse rendering it's reporting unusable.
Another challenge in the replication is that up to this point both facilities have been writing to the same tables (because they are the same server) in the warehousing db. The reporting is set up to separate the data based on indicators throughout the data, apparently.
So at this point I'm beginning to wonder if there's a way to get Transactional Replication from two separate servers writing to the same tables, given that they won't be doing the same work and sending over the same records.
I realize this is NOT recommended, and certainly not ideal. But it may present a functional option that the group can consider as at least feasible, if it's at all possible.
So, can two servers write to the same tables in Transactional Replication? Is that something folks are doing?
Thank you so much for any and all comments.