We are using merge replication with 600 users over a nationwide wan/lan
network. For the most part it works, but occasionally some changes will not
be merged to the agent. All changes make it to the server, but when users
sync the changes do not come down to them. Someitmes if they do multiple
syncs in succession they will make it but other times not. We do a snapshot
of the database nightly that is used by new users to get the initial
database. We have noticed on one user where they installed the snapshot but
did not immediately sync afterwards (we instruct them to so so that they
will get any changes since the snapsot was created). They sync'ed the next
day after a new snapshot was created.. Changes in the database from the
snapshot downloaded one day to the creation of the new sanpshot will not
sync to the database. Changes after the second snapsot is created will
sync. It appears the the client DB thinks it has the records and does not
need to get them. Any thoughts?
Can you run validation on a couple of your subscribers and let us know the
results? Are you using filtering or does each subscriber receive the same
set of data? What build of SQL Server are your subscribers and publishers
on?
Philip Vaughn
This posting is provided "AS IS" with no warranties, and confers no rights.
"Fast Eddie" <e@.bellsouth.net> wrote in message
news:VjA_d.35353$6g7.31842@.bignews1.bellsouth.net. ..
> We are using merge replication with 600 users over a nationwide wan/lan
> network. For the most part it works, but occasionally some changes will
> not be merged to the agent. All changes make it to the server, but when
> users sync the changes do not come down to them. Someitmes if they do
> multiple syncs in succession they will make it but other times not. We do
> a snapshot of the database nightly that is used by new users to get the
> initial database. We have noticed on one user where they installed the
> snapshot but did not immediately sync afterwards (we instruct them to so
> so that they will get any changes since the snapsot was created). They
> sync'ed the next day after a new snapshot was created.. Changes in the
> database from the snapshot downloaded one day to the creation of the new
> sanpshot will not sync to the database. Changes after the second snapsot
> is created will sync. It appears the the client DB thinks it has the
> records and does not need to get them. Any thoughts?
>
|||There is no filtering, all users get all data. We are using SQLServer 2000.
We confirmed today that the issue is the data lost between the creation of
the snapshots. When a new snapshot is created, data that is the new
snapshot but not in the snapshot downloaded will not syncronize if a sync
was not performed immediately after the snapshot is loaded. Any settings
that would cause this behavior?
lip Vaughn" <philipv@.microsoft.com> wrote in message
news:OSAMikALFHA.3552@.TK2MSFTNGP12.phx.gbl...
> Can you run validation on a couple of your subscribers and let us know the
> results? Are you using filtering or does each subscriber receive the same
> set of data? What build of SQL Server are your subscribers and publishers
> on?
> Philip Vaughn
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Fast Eddie" <e@.bellsouth.net> wrote in message
> news:VjA_d.35353$6g7.31842@.bignews1.bellsouth.net. ..
>
|||Can you respond back with the version of your publisher and subscriber(s)?
Philip Vaughn
This posting is provided "as is" with no warranties and confers no rights.
"Fast Eddie" <e@.bellsouth.net> wrote in message
news:X5K_d.38774$c72.11001@.bignews3.bellsouth.net. ..
> There is no filtering, all users get all data. We are using SQLServer
> 2000. We confirmed today that the issue is the data lost between the
> creation of the snapshots. When a new snapshot is created, data that is
> the new snapshot but not in the snapshot downloaded will not syncronize if
> a sync was not performed immediately after the snapshot is loaded. Any
> settings that would cause this behavior?
>
> lip Vaughn" <philipv@.microsoft.com> wrote in message
> news:OSAMikALFHA.3552@.TK2MSFTNGP12.phx.gbl...
>
Showing posts with label occasionally. Show all posts
Showing posts with label occasionally. Show all posts
Wednesday, March 21, 2012
Merge replication question
Labels:
database,
lannetwork,
merge,
microsoft,
mysql,
nationwide,
notbe,
occasionally,
oracle,
replication,
server,
sql,
users,
wan
Saturday, February 25, 2012
Merge Replication Architecture Planning Guidance
Hi,
My organization is considering use of merge replication (SQL Server 2K with MSDE clients) to implement a classic data-centric "occasionally connected" application pattern. The target user base extends to 4,500 users distributed across time zones and lang
uages. Depending on their location users will connect over telecom links varying from 28.8Kbps to broadband.
Our preference is to retain a single, centralized SQL Server cluster as a publisher and to deploy multiple remote distributor nodes to optimize performance. However, I've been unable to find a comprehensive capacity planning guide that can help us to det
ermine a) whether our proposed architecture is viable and b) how and where we should deploy distributor notes to optimize use of available processing capacity and bandwidth.
If anyone is aware of such a guide, or has first-hand operational experience of a deployment commensurate with that described above then I'd love to hear about it.
Cheers,
Lee.
Lee,
this article details scaling upto 2000 subscribers. I don't know of any
other articles that suit your needs, although Hilary once mentioned a
presentation at SQLPASS or TECHNET conference that sounds as though it'd be
useful to you. He posted the name of the presenter but unfortunately Idon't
recall it. No doubt he'll post a reply here.
Rgds,
Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I don't recall such a presentation. However the presentations done by Bren
Newman, Philip Vaughn, Matt Hollingsworth, and Kevin Collins (for SQL CE
replication) are excellent.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23DSrOufuEHA.1292@.TK2MSFTNGP10.phx.gbl...
> Lee,
> this article details scaling upto 2000 subscribers. I don't know of any
> other articles that suit your needs, although Hilary once mentioned a
> presentation at SQLPASS or TECHNET conference that sounds as though it'd
be
> useful to you. He posted the name of the presenter but unfortunately
Idon't
> recall it. No doubt he'll post a reply here.
> Rgds,
> Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Yes this is the conference proceedings I was thinking of
but apologies as I was thinking the presentations were
about MSDE rather than CE.
Rgds,
Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Actually, I believe I have heard of an installation with 4500 subscribers
where they used republishing; I think its Barnes and Noble or Ticketmaster,
and IIRC it was with SQL 7.
I urge you to contact PSS for more information on this, and how to deploy
such a topology.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:016301c4ba68$ebf53fa0$a401280a@.phx.gbl...
> Yes this is the conference proceedings I was thinking of
> but apologies as I was thinking the presentations were
> about MSDE rather than CE.
> Rgds,
> Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Thanks folks,
I do foresee that we'll be working with PSS (and most likely with MS
Consulting Svs also). This posting was intended to help me start to
understand whether we'd be pushing the envelope into areas in which other
have feared to tread (or have been badly burnt). Hopefully MS will be able
to help us understand how B&N and/or Tickermaster had planned their
topologies etc.
Many thanks for your help - and looking forward to your Merge Replication
book becoming available.
Lee.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23%23AhvfouEHA.3972@.TK2MSFTNGP15.phx.gbl...
> Actually, I believe I have heard of an installation with 4500 subscribers
> where they used republishing; I think its Barnes and Noble or
> Ticketmaster,
> and IIRC it was with SQL 7.
> I urge you to contact PSS for more information on this, and how to deploy
> such a topology.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:016301c4ba68$ebf53fa0$a401280a@.phx.gbl...
>
|||Lee,
once you've got it all set up, if you can find the time
please post up a bit of general info on the topology
choices etc.
Rgds,
Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
My organization is considering use of merge replication (SQL Server 2K with MSDE clients) to implement a classic data-centric "occasionally connected" application pattern. The target user base extends to 4,500 users distributed across time zones and lang
uages. Depending on their location users will connect over telecom links varying from 28.8Kbps to broadband.
Our preference is to retain a single, centralized SQL Server cluster as a publisher and to deploy multiple remote distributor nodes to optimize performance. However, I've been unable to find a comprehensive capacity planning guide that can help us to det
ermine a) whether our proposed architecture is viable and b) how and where we should deploy distributor notes to optimize use of available processing capacity and bandwidth.
If anyone is aware of such a guide, or has first-hand operational experience of a deployment commensurate with that described above then I'd love to hear about it.
Cheers,
Lee.
Lee,
this article details scaling upto 2000 subscribers. I don't know of any
other articles that suit your needs, although Hilary once mentioned a
presentation at SQLPASS or TECHNET conference that sounds as though it'd be
useful to you. He posted the name of the presenter but unfortunately Idon't
recall it. No doubt he'll post a reply here.
Rgds,
Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I don't recall such a presentation. However the presentations done by Bren
Newman, Philip Vaughn, Matt Hollingsworth, and Kevin Collins (for SQL CE
replication) are excellent.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23DSrOufuEHA.1292@.TK2MSFTNGP10.phx.gbl...
> Lee,
> this article details scaling upto 2000 subscribers. I don't know of any
> other articles that suit your needs, although Hilary once mentioned a
> presentation at SQLPASS or TECHNET conference that sounds as though it'd
be
> useful to you. He posted the name of the presenter but unfortunately
Idon't
> recall it. No doubt he'll post a reply here.
> Rgds,
> Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Yes this is the conference proceedings I was thinking of
but apologies as I was thinking the presentations were
about MSDE rather than CE.
Rgds,
Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Actually, I believe I have heard of an installation with 4500 subscribers
where they used republishing; I think its Barnes and Noble or Ticketmaster,
and IIRC it was with SQL 7.
I urge you to contact PSS for more information on this, and how to deploy
such a topology.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:016301c4ba68$ebf53fa0$a401280a@.phx.gbl...
> Yes this is the conference proceedings I was thinking of
> but apologies as I was thinking the presentations were
> about MSDE rather than CE.
> Rgds,
> Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Thanks folks,
I do foresee that we'll be working with PSS (and most likely with MS
Consulting Svs also). This posting was intended to help me start to
understand whether we'd be pushing the envelope into areas in which other
have feared to tread (or have been badly burnt). Hopefully MS will be able
to help us understand how B&N and/or Tickermaster had planned their
topologies etc.
Many thanks for your help - and looking forward to your Merge Replication
book becoming available.
Lee.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23%23AhvfouEHA.3972@.TK2MSFTNGP15.phx.gbl...
> Actually, I believe I have heard of an installation with 4500 subscribers
> where they used republishing; I think its Barnes and Noble or
> Ticketmaster,
> and IIRC it was with SQL 7.
> I urge you to contact PSS for more information on this, and how to deploy
> such a topology.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:016301c4ba68$ebf53fa0$a401280a@.phx.gbl...
>
|||Lee,
once you've got it all set up, if you can find the time
please post up a bit of general info on the topology
choices etc.
Rgds,
Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Labels:
architecture,
classic,
clients,
considering,
data-centric,
database,
guidance,
implement,
merge,
microsoft,
msde,
mysql,
occasionally,
oracle,
organization,
planning,
replication,
server,
sql
Subscribe to:
Posts (Atom)