August 23, 2010 at 10:04 am
I've been tasked with a push replication, as well as a merge replication on the same database... let me explain:
Push replication: 10 of 11 tables, sps, udfs, etc on Server1.Database1 needs to be 'pushed' out to two other servers. These servers cannot directly pull the data from Server1, and are not allowed to update the data that is being pushed out to them (or if they do, it's auto-removed/overwritten).
Merge replication: The other 1 table needs to be set up with merge replication, so that Server2 and Server3 can update the data as well. The table is set up with a uniqueIdentifier column for this purpose.
I'm wary about 'Just doing it' as these are production servers. I do not have a development system that I can test this out on to see the affects.
Please let me know:
1.) Is this possible.
2.) What affects are going to happen to the current replicated database (IE: will it be dropped/recreated when I set up the merge replication?)
3.) Any problems or other concerns that I would need to address.
Thanks!
August 23, 2010 at 2:38 pm
jf577 (8/23/2010)
I've been tasked with a push replication, as well as a merge replication on the same database... let me explain:Push replication: 10 of 11 tables, sps, udfs, etc on Server1.Database1 needs to be 'pushed' out to two other servers. These servers cannot directly pull the data from Server1, and are not allowed to update the data that is being pushed out to them (or if they do, it's auto-removed/overwritten).
Merge replication: The other 1 table needs to be set up with merge replication, so that Server2 and Server3 can update the data as well. The table is set up with a uniqueIdentifier column for this purpose.
I'm wary about 'Just doing it' as these are production servers. I do not have a development system that I can test this out on to see the affects.
Please let me know:
1.) Is this possible.
2.) What affects are going to happen to the current replicated database (IE: will it be dropped/recreated when I set up the merge replication?)
3.) Any problems or other concerns that I would need to address.
Thanks!
1. Yes, it is possible.
2. When you state the current replicated database, I am assuming you are talking about the subscriber. The answer yes it will be dropped and recreated UNLESS you decide you want to initialize manually (i.e. don't have the create subscription steps generate and apply the snapshot). However, you are likely to have problems doing it this way.
3. Concerns. None really. I would recommend that you do some testing / configuring on a test server first and being that you don't have one I would recommend maybe a local install or two to try it out. There are some nuances that you should be comfortable with prior to implementing in production.
Another concern is that you state "(or if they do, it's auto-removed/overwritten)" about data changes at the subscriber for your "push" (transactional) publication. You can make changes at the subscriber and it will not be auto-updated back to what it was originally so, if you do not want those changes occurring at the subscriber then you should take steps to ensure that it doesn't happen.
Always available to answer more questions as needed.
Hope this helps.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply