| Groups | Blog | Home |
sql server replication : Complete newbie to replication, have a question
recently to have a server setup in LocationB due to some bandwidth issues. LocationB was given a snapshot of the DB @ LocationA when it was first setup. However, both machines will need to have the same data as both are used in a production environment. I will probably want to do this nightly. I have read a lot of posts and webistes, but still am semi in the dark. About the only thing i've figured out (i think) is that I will need to do some sort of merge replicaiton. What do I need to do to get started, a link to a HOW TO for a smiliar setup would be great. I have read a bit and some mention having a 3rd server, do i need a 3rd server as the final merged server? I guess more importantly is a 3rd server an optimal solution? Any help would be greatly appreciated.
Forgot to mention, I am running SQL Server 2000 on both servers.
[quoted text, click to view] "Lucas Graf" <lgraf2000@comcast.net> wrote in message news:OjZ0E0bQGHA.5296@TK2MSFTNGP09.phx.gbl... > We have had a server in LocationA for quite some time. The need arose > recently to have a server setup in LocationB due to some bandwidth issues. > > LocationB was given a snapshot of the DB @ LocationA when it was first > setup. However, both machines will need to have the same data as both are > used in a production environment. I will probably want to do this > nightly. > > I have read a lot of posts and webistes, but still am semi in the dark. > About the only thing i've figured out (i think) is that I will need to do > some sort of merge replicaiton. > > What do I need to do to get started, a link to a HOW TO for a smiliar > setup would be great. I have read a bit and some mention having a 3rd > server, do i need a 3rd server as the final merged server? I guess more > importantly is a 3rd server an optimal solution? > > Any help would be greatly appreciated. > >
In merge replication you will have Distributor, Publisher and Subscriber.
They are different roles for a replication setup but they can be on the same physical machine. I think the 3rd server you mentioned is distributor. You can setup the distributor on the same server with the publisher, so you don't need a third machine. Yi Chen [quoted text, click to view] "Lucas Graf" <lgraf2000@comcast.net> wrote in message news:OjZ0E0bQGHA.5296@TK2MSFTNGP09.phx.gbl... > We have had a server in LocationA for quite some time. The need arose > recently to have a server setup in LocationB due to some bandwidth issues. > > LocationB was given a snapshot of the DB @ LocationA when it was first > setup. However, both machines will need to have the same data as both are > used in a production environment. I will probably want to do this > nightly. > > I have read a lot of posts and webistes, but still am semi in the dark. > About the only thing i've figured out (i think) is that I will need to do > some sort of merge replicaiton. > > What do I need to do to get started, a link to a HOW TO for a smiliar > setup would be great. I have read a bit and some mention having a 3rd > server, do i need a 3rd server as the final merged server? I guess more > importantly is a 3rd server an optimal solution? > > Any help would be greatly appreciated. > >
Ok. That makes sense. I have been messing around trying to set it up today, and am still lost. Currently the 2 servers are out of sync. Both have data the other doesn't. What do I need to do to get them both to have the same data now, and then keep them replciating from here on out? [quoted text, click to view] "Yi Chen [MSFT]" <yiche@online.microsoft.com> wrote in message news:%23o7jSucQGHA.1204@TK2MSFTNGP12.phx.gbl... > In merge replication you will have Distributor, Publisher and Subscriber. > They are different roles for a replication setup but they can be on the > same physical machine. I think the 3rd server you mentioned is > distributor. You can setup the distributor on the same server with the > publisher, so you don't need a third machine. > > Yi Chen > > "Lucas Graf" <lgraf2000@comcast.net> wrote in message > news:OjZ0E0bQGHA.5296@TK2MSFTNGP09.phx.gbl... >> We have had a server in LocationA for quite some time. The need arose >> recently to have a server setup in LocationB due to some bandwidth >> issues. >> >> LocationB was given a snapshot of the DB @ LocationA when it was first >> setup. However, both machines will need to have the same data as both >> are used in a production environment. I will probably want to do this >> nightly. >> >> I have read a lot of posts and webistes, but still am semi in the dark. >> About the only thing i've figured out (i think) is that I will need to do >> some sort of merge replicaiton. >> >> What do I need to do to get started, a link to a HOW TO for a smiliar >> setup would be great. I have read a bit and some mention having a 3rd >> server, do i need a 3rd server as the final merged server? I guess more >> importantly is a 3rd server an optimal solution? >> >> Any help would be greatly appreciated. >> >> > >
[quoted text, click to view] Lucas Graf wrote:
> We have had a server in LocationA for quite some time. The need arose > recently to have a server setup in LocationB due to some bandwidth issues. > > LocationB was given a snapshot of the DB @ LocationA when it was first > setup. However, both machines will need to have the same data as both are > used in a production environment. I will probably want to do this nightly. > > I have read a lot of posts and webistes, but still am semi in the dark. > About the only thing i've figured out (i think) is that I will need to do > some sort of merge replicaiton. > > What do I need to do to get started, a link to a HOW TO for a smiliar setup > would be great. I have read a bit and some mention having a 3rd server, do > i need a 3rd server as the final merged server? I guess more importantly is > a 3rd server an optimal solution? > > Any help would be greatly appreciated.
Lucas,
presumably you have initialized the subscriber and are using merge replication? If so, you just need to synchronize the subscriber to have the data merged. You'll need to consider who should win conflicts (publisher by default) and if conflicts should be allowed (filtering). Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book: http://www.nwsu.com/0974973602p.html)
Ok.
I got this far and was tentative on going further. I will keep trucking and see what else may come up that causes issues. Thanks for the help so far, I hope to report back a positive experience. [quoted text, click to view] "Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message news:%23ogHO4uQGHA.2628@TK2MSFTNGP15.phx.gbl... > Lucas, > presumably you have initialized the subscriber and are using merge > replication? If so, you just need to synchronize the subscriber to have > the data merged. You'll need to consider who should win conflicts > (publisher by default) and if conflicts should be allowed (filtering). > Cheers, > Paul Ibison SQL Server MVP, www.replicationanswers.com > (recommended sql server 2000 replication book: > http://www.nwsu.com/0974973602p.html) > >
I guess I am still confused w/the whole publisher/distributor thing.
Since I want both servers to merge both of their data are they both set to publishers and distributors? Or is only 1 a publisher and both distributors and subscribers? So confused.. :( [quoted text, click to view] "Lucas Graf" <lgraf2000@comcast.net> wrote in message news:Ob$pMuzQGHA.2436@TK2MSFTNGP11.phx.gbl... > Ok. > I got this far and was tentative on going further. I will keep trucking > and see what else may come up that causes issues. Thanks for the help so > far, I hope to report back a positive experience. > > > "Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message > news:%23ogHO4uQGHA.2628@TK2MSFTNGP15.phx.gbl... >> Lucas, >> presumably you have initialized the subscriber and are using merge >> replication? If so, you just need to synchronize the subscriber to have >> the data merged. You'll need to consider who should win conflicts >> (publisher by default) and if conflicts should be allowed (filtering). >> Cheers, >> Paul Ibison SQL Server MVP, www.replicationanswers.com >> (recommended sql server 2000 replication book: >> http://www.nwsu.com/0974973602p.html) >> >> > >
Ok.
ServerA I have set him to a Distributor, Publisher and set the Database i want to publish to the other server as the "push" datatabase. All seems good on ServerA. ServerB Not sure what to do here so its data gets pushed to ServerA to be merged there as well. Everything I try i end up getting the error "You cannot create a merge replicaion in database xxxc. The database contains one or more merge subscritptions that are anonymous or that use the Priority of the Publisher when resolving conflicts." [quoted text, click to view] "Lucas Graf" <lgraf@nvidia.com> wrote in message news:uSQuaI8QGHA.5552@TK2MSFTNGP14.phx.gbl... >I guess I am still confused w/the whole publisher/distributor thing. > > Since I want both servers to merge both of their data are they both set to > publishers and distributors? Or is only 1 a publisher and both > distributors and subscribers? > > So confused.. :( > > > "Lucas Graf" <lgraf2000@comcast.net> wrote in message > news:Ob$pMuzQGHA.2436@TK2MSFTNGP11.phx.gbl... >> Ok. >> I got this far and was tentative on going further. I will keep trucking >> and see what else may come up that causes issues. Thanks for the help so >> far, I hope to report back a positive experience. >> >> >> "Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message >> news:%23ogHO4uQGHA.2628@TK2MSFTNGP15.phx.gbl... >>> Lucas, >>> presumably you have initialized the subscriber and are using merge >>> replication? If so, you just need to synchronize the subscriber to have >>> the data merged. You'll need to consider who should win conflicts >>> (publisher by default) and if conflicts should be allowed (filtering). >>> Cheers, >>> Paul Ibison SQL Server MVP, www.replicationanswers.com >>> (recommended sql server 2000 replication book: >>> http://www.nwsu.com/0974973602p.html) >>> >>> >> >> > >
Maybe Bidirectional Transactional Replication is more what I am looking for?
[quoted text, click to view] "Lucas Graf" <lgraf@nvidia.com> wrote in message news:uSQuaI8QGHA.5552@TK2MSFTNGP14.phx.gbl... >I guess I am still confused w/the whole publisher/distributor thing. > > Since I want both servers to merge both of their data are they both set to > publishers and distributors? Or is only 1 a publisher and both > distributors and subscribers? > > So confused.. :( > > > "Lucas Graf" <lgraf2000@comcast.net> wrote in message > news:Ob$pMuzQGHA.2436@TK2MSFTNGP11.phx.gbl... >> Ok. >> I got this far and was tentative on going further. I will keep trucking >> and see what else may come up that causes issues. Thanks for the help so >> far, I hope to report back a positive experience. >> >> >> "Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message >> news:%23ogHO4uQGHA.2628@TK2MSFTNGP15.phx.gbl... >>> Lucas, >>> presumably you have initialized the subscriber and are using merge >>> replication? If so, you just need to synchronize the subscriber to have >>> the data merged. You'll need to consider who should win conflicts >>> (publisher by default) and if conflicts should be allowed (filtering). >>> Cheers, >>> Paul Ibison SQL Server MVP, www.replicationanswers.com >>> (recommended sql server 2000 replication book: >>> http://www.nwsu.com/0974973602p.html) >>> >>> >> >> > >
Lucas,
this thread is becoming a bit too wide so let's take a step back. Can you explain what are the business requirements in some detail. You have data on Server A and you want to replicate it to server B. Can both servers change the data (presumably yes). Can they change the same data? Are they always connected, or server B is sometimes offline? What degree of latency can you afford? etc Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book: http://www.nwsu.com/0974973602p.html)
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
October 2008
| home · blog · groups | Questions? Comments? Contact the dn |