Replication Solution
in [Replication]
|
From: Mike 'Spike' Lovell on 16 Oct 2009 22:03 I have a requirements to setup 2 SQL servers, and replicate databases between them 'but' allow changes to the tables, views, stored procedures etc... As far as I know, I can't use P2P Replication because the database schema must be the same at both ends, so the client will not be able to make changes (add/remove/edit tables for example). There's no shared storage available, is there a way I can achieve replication between the two without the above constraints? Thanks ~ Mike
From: Paul Ibison on 17 Oct 2009 04:11 P2P won't allow changes to the same rows on each side - if you need this then merge replication should be used. Merge replication will allow for you adding new articles and changing existing ones at the publisher and the changes will get propagated to the subscriber. You won't be able to remove tables without recreating the publication though. HTH, Paul Ibison
From: Mike 'Spike' Lovell on 17 Oct 2009 11:49 -------------------------------------------------- > P2P won't allow changes to the same rows on each side - if you need this > then merge replication should be used. > Merge replication will allow for you adding new articles and changing > existing ones at the publisher and the changes will get propagated to the > subscriber. You won't be able to remove tables without recreating the > publication though. > HTH, > Paul Ibison Thanks for the reply, Yes, that's my biggest problem unfortunately. I need the ability to add/remove tables and modify their structure whilst keeping the replication in tact (all without clustering). ~ Mike
|
Pages: 1 Prev: 55 Opinion Dsiconsolas.com Next: SQL2008 Replication / synchronization with SQL Express Editon |