| Groups | Blog | Home |
sql server replication : Multiple master replication? Does SQL2005 have it? Do I want it?
I'm closely examining the pattern http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpatterns/html/ArcDataReplication.asp I have a 'Composite Movement Set' and a situation similar to the 'Complex Data Movement for Reporting Purposes, Figure 4'. Specifically, N databases residing locally on computers A(1) thru A(N) (i.e. one DB/computer) 1 'central' computer with a Database, let's say B. I must get the data from databases A(1) thru A(N) into B. All schemas are identical. Unique guids are used for primary keys. I see references on the web to desired DBMS solutions with 'multiple master-single slave replication', where DBs sitting on multiple servers can be replicated to a single DB sitting on yet another server. I understand that specific answers on my exact situation may be difficult, so my questions are... 1) Does SQL2005 support something akin to 'multiple master-single slave replication? (I have looked but cannot find the answer.) 2) If SQL2005 does support this, is this a possible implementation of the 'Move Copy of Data Pattern' that I provide the link to above. Thank you very much for your help. -- Allan Michaels
Have a look at peer-to-peer replication.
-- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Allan Michaels" <allanm@newsgroups.nospam> wrote in message news:2213B061-867D-42CC-A6C1-532396345314@microsoft.com... > Hello, > > I'm closely examining the pattern > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpatterns/html/ArcDataReplication.asp > > I have a 'Composite Movement Set' and a situation similar to the > 'Complex Data Movement for Reporting Purposes, Figure 4'. > Specifically, > N databases residing locally on computers A(1) thru A(N) (i.e. one > DB/computer) > 1 'central' computer with a Database, let's say B. > > I must get the data from databases A(1) thru A(N) into B. > All schemas are identical. Unique guids are used for primary keys. > > I see references on the web to desired DBMS solutions with 'multiple > master-single slave replication', where DBs sitting on multiple servers > can > be replicated to a > single DB sitting on yet another server. > > I understand that specific answers on my exact situation may be difficult, > so my questions are... > > 1) Does SQL2005 support something akin to 'multiple master-single slave > replication? (I have looked but cannot find the answer.) > > 2) If SQL2005 does support this, is this a possible implementation of the > 'Move Copy of Data Pattern' that I provide the link to above. > > Thank you very much for your help. > > -- > Allan Michaels > Ann Arbor, MI
Hello Hilary,
Thank you for your suggestion. My first question in my post was: [quoted text, click to view] >1) Does SQL2005 support something akin to 'multiple master-single slave >replication? Just to be clear, does SQL2005 support multiple-master servers replicating to a single slave server? (From you answer, it seems that it does not.) Continuing with your suggestion...according to: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpatterns/html/DpGlossary.asp peer-to-peer replication is another name for master-master replication. I don't believe this applies. My data need only travel one way--from the lower-tier Database A(n) to the higher-tier Database B. Also, the lower-tier has n databases ( A(1)...A(n)), not just a single database. I really do appreciate your input and value your comments. I will carefully look into any thoughts you have on my situation. Thank you very much for your time. -- Allan Michaels Ann Arbor, MI [quoted text, click to view] "Hilary Cotter" wrote:
> Have a look at peer-to-peer replication. > > -- > Hilary Cotter > Director of Text Mining and Database Strategy > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. > > This posting is my own and doesn't necessarily represent RelevantNoise's > positions, strategies or opinions. > > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > > > > "Allan Michaels" <allanm@newsgroups.nospam> wrote in message > news:2213B061-867D-42CC-A6C1-532396345314@microsoft.com... > > Hello, > > > > I'm closely examining the pattern > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpatterns/html/ArcDataReplication.asp > > > > I have a 'Composite Movement Set' and a situation similar to the > > 'Complex Data Movement for Reporting Purposes, Figure 4'. > > Specifically, > > N databases residing locally on computers A(1) thru A(N) (i.e. one > > DB/computer) > > 1 'central' computer with a Database, let's say B. > > > > I must get the data from databases A(1) thru A(N) into B. > > All schemas are identical. Unique guids are used for primary keys. > > > > I see references on the web to desired DBMS solutions with 'multiple > > master-single slave replication', where DBs sitting on multiple servers > > can > > be replicated to a > > single DB sitting on yet another server. > > > > I understand that specific answers on my exact situation may be difficult, > > so my questions are... > > > > 1) Does SQL2005 support something akin to 'multiple master-single slave > > replication? (I have looked but cannot find the answer.) > > > > 2) If SQL2005 does support this, is this a possible implementation of the > > 'Move Copy of Data Pattern' that I provide the link to above. > > > > Thank you very much for your help. > > > > -- > > Allan Michaels > > Ann Arbor, MI > >
Hi Allan,
Basicly, there is no multiple-master single slave concept in SQL Server. However, you could implement by some other technical. In SQL Server you can use peer-to-peer replication and set up several peers and define the destination database to be the same. In this scenario, if your source databases will conflict with some record as in the primary keys, you may use the Merge replication to check the conflicts. Here is a Books online article about the Merge replication: Merge Replication Overview http://msdn2.microsoft.com/en-us/library/ms152746(SQL.90).aspx Hope this will be helpful! Sincerely, Wei Lu Microsoft Online Community Support ================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Thank you for your response Wei Lu.
I'll dig into the multiple peers with a single destination concept. It might take me until next week Wednesday or Thursday. Then I might have some more detailed questions. Thanks again for your time. -- Allan Michaels Ann Arbor, MI [quoted text, click to view] "Wei Lu" wrote:
> Hi Allan, > > Basicly, there is no multiple-master single slave concept in SQL Server. > However, you could implement by some other technical. > > In SQL Server you can use peer-to-peer replication and set up several peers > and define the destination database to be the same. > > In this scenario, if your source databases will conflict with some record > as in the primary keys, you may use the Merge replication to check the > conflicts. > > Here is a Books online article about the Merge replication: > > Merge Replication Overview > http://msdn2.microsoft.com/en-us/library/ms152746(SQL.90).aspx > > Hope this will be helpful! > > Sincerely, > > Wei Lu > Microsoft Online Community Support > > ================================================== > > When responding to posts, please "Reply to Group" via your newsreader so > that others may learn and benefit from your issue. > > ================================================== > This posting is provided "AS IS" with no warranties, and confers no rights. >
Thanks Wei Lu.
I've digested the peer-to-peer info, and I thank you for the suggestions. Your help was very much appreciated. -- Allan Michaels Ann Arbor, MI [quoted text, click to view] "Allan Michaels" wrote:
> Thank you for your response Wei Lu. > > I'll dig into the multiple peers with a single destination concept. > It might take me until next week Wednesday or Thursday. > Then I might have some more detailed questions. > > Thanks again for your time. > > -- > Allan Michaels > Ann Arbor, MI > > > "Wei Lu" wrote: > > > Hi Allan, > > > > Basicly, there is no multiple-master single slave concept in SQL Server. > > However, you could implement by some other technical. > > > > In SQL Server you can use peer-to-peer replication and set up several peers > > and define the destination database to be the same. > > > > In this scenario, if your source databases will conflict with some record > > as in the primary keys, you may use the Merge replication to check the > > conflicts. > > > > Here is a Books online article about the Merge replication: > > > > Merge Replication Overview > > http://msdn2.microsoft.com/en-us/library/ms152746(SQL.90).aspx > > > > Hope this will be helpful! > > > > Sincerely, > > > > Wei Lu > > Microsoft Online Community Support > > > > ================================================== > > > > When responding to posts, please "Reply to Group" via your newsreader so > > that others may learn and benefit from your issue. > > > > ================================================== > > This posting is provided "AS IS" with no warranties, and confers no rights. > >
Hi Allan,
Thanks for the update. Glad to hear that the information is helpful. If you have any questions or concerns, please feel free to let us know. Have a great day. Sincerely, Wei Lu Microsoft Online Community Support ================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |