Friday, March 30, 2012
Merge Replication.
I have two DBs that are the same, the two of them are on two separated networks, update happens in the both of them and i need to keep them both the same, (replicated) how can i copy changes from one to other and other to one ;)
anybody has an idea?
thanks,Refer to SQL server books online for information on Merge Replication which is suitable for your task, if not you can use Transactional replication.
Make sure both the servers can see each other in order to function the replication.|||This is the main problem,
they can't see each other, they are on separated networks.
I can only transfer files between them.
thanks,|||Originally posted by hushpappy
This is the main problem,
they can't see each other, they are on separated networks.
I can only transfer files between them.
thanks,
Build custom (handmade) replication with DTS.|||Do you have any sample for this kind of thing?
thanks,|||Originally posted by hushpappy
Do you have any sample for this kind of thing?
thanks,
I have no sample for your case (I implemented custom replications for different schemas). Just couple suggestions about how it is possible to do.
1. Use GUI (globally unique identifiers) as primary or unique key for your tables.
2. Because of type replication (something like merge) it needs to have conflict resolver (who is main updater).
3. Create "distribution" database on every server (includes replicated tables twice IN and OUT - empty for first time).
4. Setup triggers on replicated tables (with flag - not fire if update was done by "merge" agent).
5. Add (if not exists) field like last update time to replicated tables.
6. Create "merge" agent for applying changes.
By using DTS you could export data (OUT) from source server to disk (move it to another server ) and import data (IN) to target server.
Update data on target with using conflict resolver. Repeat the same in another direction.
Of course it is just draft for custom replication - real model may be more complicated.|||Originally posted by hushpappy
This is the main problem,
they can't see each other, they are on separated networks.
I can only transfer files between them.
thanks,
You can use merge replication when the two sql servers are on non-trusted networks.
First, the SQL Server Agents must be running under the same user name. This may require you create identical local accounts on both machines to use as the SQL Service agent service Log On account.
Next, on the publisher, add a TCP/IP alias to the subscriber using the Client Network Utility. The server alias needs to be the machine name of the subscriber, and the server name needs to be the IP address of the subscriber.
Finally, create the merge publication and push subscription.
Monday, March 26, 2012
merge replication w PocketPC and trigger order
We've got a problen in a customer with SQL Server 2000 SP3 and merge
replication with PocketPC
We have some triggers FOR UPDATE on the same field used to distribute in
replication settings, so I suspect sometimes our triggers didn't work, and
sometimes the first trigger that has been executed were the replication
trigger.
Can I use the sp_settriggerorder to set the order to execute, setting the
replication trihgger as last in execution?
Thanks
Yes you can, I normally make them execute first though.
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
"Ricardo Snchez" <Ricardo Snchez@.discussions.microsoft.com> wrote in
message news:2BA27F4E-0454-4DC0-9DC2-46CD14C7E368@.microsoft.com...
> Hi
> We've got a problen in a customer with SQL Server 2000 SP3 and merge
> replication with PocketPC
> We have some triggers FOR UPDATE on the same field used to distribute in
> replication settings, so I suspect sometimes our triggers didn't work, and
> sometimes the first trigger that has been executed were the replication
> trigger.
> Can I use the sp_settriggerorder to set the order to execute, setting the
> replication trihgger as last in execution?
> Thanks
sql
Merge Replication updating SP3 to SP4
I am planning to update SP3 to SP4 on a replicated server.
A- Please correct me if i wrong in order.
1- Apply SP4 on Publisher / Distributor (on single box)
2- All subscribers.
B- As per my knowledge there are no issues while applying SP4. Is there any
known issue while applying the sp4 has to be taken care of?
TIA
Regards
Javed Iqbal
Javed,
I agree with the order. I've had a search of this newsgroup (using Google
Groups) to check for sp4 and there are hardly any reported errors so far.
The main on e is
http://groups.google.com/group/micro...85 a5a37097d4
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Merge replication update timing
with laptops. I made some data changes on the Publisher and then synched
with the laptop and it got the new data. Then, I added a test table and 2
rows of data on the Publisher. After a few minutes I tried to synch again
and did not get the table changes. Is there something I have to do with the
Snapshot Agent in order to make that new table and data get to the laptop?
Thanks.
David
David - you'll need to run the snapshot agent then the merge agent to have
this new table included.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Is there a way that I can do this with system stored procedure? if so,
do you know what they are? e.g. sp_?
Thanks.
David
*** Sent via Developersdex http://www.codecomments.com ***
|||David - sp_start_job.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Boy, when I create Microsoft Access replication it just automatically
grabbed the new table and data without me doing anything. I guess SQL
Server takes more work?
David
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OvgdFn1$FHA.1028@.TK2MSFTNGP11.phx.gbl...
> David - sp_start_job.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Paul,
How do I run the Merge Agent manually? Can I do it in EM? I was able to
run the Snapshot Agent but I do not see where I can run the Merge Agent.
Can you help?
p.s. The same server is both publisher and Distributor, if that helps.
David
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OvgdFn1$FHA.1028@.TK2MSFTNGP11.phx.gbl...
> David - sp_start_job.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Interesting - I never knew Access did this. I'm not too sure that this is
ideal though. If you added a completely unrelated and large table it would
be a pain if it was automatically added.
Cheers,
Paul
"David" <dlchase@.lifetimeinc.com> wrote in message
news:OdjxfH2$FHA.3136@.TK2MSFTNGP15.phx.gbl...
> Boy, when I create Microsoft Access replication it just automatically
> grabbed the new table and data without me doing anything. I guess SQL
> Server takes more work?
> David
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:OvgdFn1$FHA.1028@.TK2MSFTNGP11.phx.gbl...
>
|||David,
you should see the merge agent when you expand the replication monitor. If
the subscription is pull, then just run the job on the subscriber (merge
agent is synonomous with a job that runs merge.exe).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Use the conflict viewer to determine if these changes were conflicts and
were rolled back.
Also are you using any filtering? It is possible that these changes where
filtered out by the filter.
Hilary Cotter
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
"David" <dlchase@.lifetimeinc.com> wrote in message
news:%23%23JQ5N0$FHA.4012@.TK2MSFTNGP10.phx.gbl...
>I am new to replication and have setup Merge replication (SQL2k) to synch
>with laptops. I made some data changes on the Publisher and then synched
>with the laptop and it got the new data. Then, I added a test table and 2
>rows of data on the Publisher. After a few minutes I tried to synch again
>and did not get the table changes. Is there something I have to do with
>the Snapshot Agent in order to make that new table and data get to the
>laptop? Thanks.
> David
>
|||I see that in Replication Monitor but it has a red X on the folder and also
on the Publishers folder. I don't know where to look for why the red X is
there. Also, ALL subscribers will be anonymous as they are laptops that
will be disconnected from the network from time to time. Did I do anything
wrong? This is my first (test) laptop and I want to get this right before
deploying into production.
p.s. Data changes are replicating, but the new table is still not getting to
the anonymous subscriber. Also, I tried running the start from the merge
agents folder and it prompted me for a username and password for the laptop
database.
David
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OUkYiy2$FHA.2652@.TK2MSFTNGP09.phx.gbl...
> David,
> you should see the merge agent when you expand the replication monitor. If
> the subscription is pull, then just run the job on the subscriber (merge
> agent is synonomous with a job that runs merge.exe).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
Monday, March 19, 2012
Merge Replication not merging updates made to subscriber
I make an update to the server that acts as the distributor the update is
reflected on the subscribers. However when I make a change on the subscriber
I cannot see it on the other subscribers or on the distributor. Any help
regarding this would be appreciated.
Thank you,
Abdul Rauf
Abdul,
how are you making the change on the subscriber? If it is a bulk insert
without firing the triggers, it won't replicate to the publisher. In some
rare other cases this also happens (eg when the filter is set to 1=2 and you
are adding records onto the subscriber. If there is no coresponding record
in MSmerge_contents try using sp_addtabletocontents to include the rows then
resynchronise. Alternatively you can use sp_mergedummyupdate for a single
row.
HTH,
Paul Ibison (SQL Server MVP)
[vbcol=seagreen]
|||Paul, I'm new to replication so I will do more research on what you have
below. I'm testing this scenario so I'm just going into the enterprise
manager of the subscriber database and updating a row in the Pubs database.
Updating a row in the Distributor database works but not in the Subscriber
through enterprise manager.
"Paul Ibison" wrote:
> Abdul,
> how are you making the change on the subscriber? If it is a bulk insert
> without firing the triggers, it won't replicate to the publisher. In some
> rare other cases this also happens (eg when the filter is set to 1=2 and you
> are adding records onto the subscriber. If there is no coresponding record
> in MSmerge_contents try using sp_addtabletocontents to include the rows then
> resynchronise. Alternatively you can use sp_mergedummyupdate for a single
> row.
> HTH,
> Paul Ibison (SQL Server MVP)
>
>
Merge replication not merging changes
I update this table and the data does not get propogated to the subscriber.
effectively, I am creating "deletes" at the subscriber by invalidating the
data (i.e., updates cause it to fall outside the filter criteria)
The initial subscription works. Then I update so the data should be removed
and it doesn't happen.
I use sp_showrowreplicainfo and I can see that the generation info at the
subscriber is lower than that at the publisher.
I initiate the merge and the data does not get removed from the subscriber.
It's very late for me, so maybe I am missing something obvious.
Suggestions appreciated
regards
Steve
To answer my own question after further experimentation, it appears to depend
completely on which table you hang the join filter off.
If the parent table has its referenced row updated, the change cascades
properly down the chain.
Wow, what a tiring lesson to learn.
"SteveM" wrote:
> my replication scenario involves a table that has a filter on three columns.
> I update this table and the data does not get propogated to the subscriber.
> effectively, I am creating "deletes" at the subscriber by invalidating the
> data (i.e., updates cause it to fall outside the filter criteria)
>
|||Generation numbers are localized to the database and article. If you have
more than one subscriber the generation values for the same article on the
publisher and subscriber can vary wildly. IIRC the generation value for the
publisher in a single subscriber topology will always be one larger than the
value on the subscriber.
Check the conflict viewer to see if there is anything there.
Hilary Cotter
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
"SteveM" <SteveM@.discussions.microsoft.com> wrote in message
news:0AC4EB4D-11DD-40C5-A1B3-7160A559B57B@.microsoft.com...
> my replication scenario involves a table that has a filter on three
> columns.
> I update this table and the data does not get propogated to the
> subscriber.
> effectively, I am creating "deletes" at the subscriber by invalidating the
> data (i.e., updates cause it to fall outside the filter criteria)
> The initial subscription works. Then I update so the data should be
> removed
> and it doesn't happen.
> I use sp_showrowreplicainfo and I can see that the generation info at the
> subscriber is lower than that at the publisher.
> I initiate the merge and the data does not get removed from the
> subscriber.
> It's very late for me, so maybe I am missing something obvious.
> Suggestions appreciated
> regards
> Steve
Merge Replication Not Accounting For Dependencies
now and then the replication process attempts to insert or update tables out
of order. For instance: We have a TransactionDocuments table that has a one
to many relationship with a TransactionLines table. Sometimes SQL Server will
attempt to instert new TransactionLines before it has inserted the
TransactionDocuments the TransactionLines depend on.
I thought merge replication was supposed to keep track of these
dependencies. If so, is there a bug that has a workaround or something else I
need to check?
Thanks,
Matt
Matt,
you could set the NOT FOR REPLICATION attribute on the FKs to true. In SQL
server 2005 it is possible to specify the merge replication order but not so
in SQL 2000. Usually the order selected in SQL Server 2000 is correct but
not always. Please check these articles:
http://www.replicationanswers.com/Me...derArticle.asp
http://support.microsoft.com/default.aspx?scid=kb;[LN];307356
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Merge replication has a rich set of features regarding dependencies, but
these are typically for sensing join filters. As Paul has pointed out child
records can be inserted before parent records, but normally these are
resolved within a batch and if not the next time the agent runs the
dependencies will be fixed as the parent will get in before the child the
second time around.
The generic work around is to use the not for replication switch on all
constraints.
Hilary Cotter
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
"Matt Sradley" <MattSradley@.discussions.microsoft.com> wrote in message
news:4C82B8F1-0176-4E6B-B0AF-D4F4F840A268@.microsoft.com...
> We have a SQL Serrver 2000 database that utilizes merge replication. Every
> now and then the replication process attempts to insert or update tables
> out
> of order. For instance: We have a TransactionDocuments table that has a
> one
> to many relationship with a TransactionLines table. Sometimes SQL Server
> will
> attempt to instert new TransactionLines before it has inserted the
> TransactionDocuments the TransactionLines depend on.
> I thought merge replication was supposed to keep track of these
> dependencies. If so, is there a bug that has a workaround or something
> else I
> need to check?
> Thanks,
> Matt
|||Thanks,
You both answered my question. It looks like the main problem are self
referencing tables in our DB. Not for replication will fix the problem. Do
you think I should do a constraint check after the replication process is
finished? It makes me nervous that data is getting put in the tables without
the checks in place.
"Hilary Cotter" wrote:
> Merge replication has a rich set of features regarding dependencies, but
> these are typically for sensing join filters. As Paul has pointed out child
> records can be inserted before parent records, but normally these are
> resolved within a batch and if not the next time the agent runs the
> dependencies will be fixed as the parent will get in before the child the
> second time around.
> The generic work around is to use the not for replication switch on all
> constraints.
> --
> Hilary Cotter
> 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
> "Matt Sradley" <MattSradley@.discussions.microsoft.com> wrote in message
> news:4C82B8F1-0176-4E6B-B0AF-D4F4F840A268@.microsoft.com...
>
>
|||Matt,
I suppose the best option is to upgrade to SQL 2005, but if this is not an
option currently for you, then it's entirely your decision about the
constraint checking after synchronization - I never do it FWIW.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Monday, March 12, 2012
Merge Replication Issue. Update not happening
We have set up merge replication between a few boxes. I make changes on one
box, replicate, and check the tables on the other box. The inserts are being
replicated, and some updates.
It appears that the updates made out of a stored proc are not being
replicated. I can manually update the table, and it will be replicated. But
when updated from the stored proc, it is not coming accrossed.
Any ideas?
Steve
More info.
sp3, no conflicts reported, after further testing, it seems one column on
one table never gets updated. Other columns that didn't, did at other times.
It is of type bit. I can manually update it and replicate, but can't have
the stored procedure update it and replicate.
"SteveInBeloit" wrote:
> Hi,
> We have set up merge replication between a few boxes. I make changes on one
> box, replicate, and check the tables on the other box. The inserts are being
> replicated, and some updates.
> It appears that the updates made out of a stored proc are not being
> replicated. I can manually update the table, and it will be replicated. But
> when updated from the stored proc, it is not coming accrossed.
> Any ideas?
> Steve
>
|||Just went to sp4, that did not help. When I do a "validate" after the
replicate, the checksum for that table fails.
"SteveInBeloit" wrote:
[vbcol=seagreen]
> More info.
> sp3, no conflicts reported, after further testing, it seems one column on
> one table never gets updated. Other columns that didn't, did at other times.
> It is of type bit. I can manually update it and replicate, but can't have
> the stored procedure update it and replicate.
>
> "SteveInBeloit" wrote:
|||More info - it is a Pull initiated at the subscriber. If I run the same
application on the Publisher, and make the updates, then replicate, the
change gets to the subscriber, just not the other way around.
"SteveInBeloit" wrote:
[vbcol=seagreen]
> Just went to sp4, that did not help. When I do a "validate" after the
> replicate, the checksum for that table fails.
> "SteveInBeloit" wrote:
|||Solved:
It was actually a delete and an insert, not an update. A record had been
written to a ##TempTable. Processing was done on that record. Then the GUID
key of that row was used to delete the row out of the real table, then and
INSERT from the temp to the real table to put it back. On that insert, I
used the same GUID key instead of letting the table NEWID get a new one. It
confused replication, having known there was a DELETE and and INSERT, but the
GUIDs the same.
"SteveInBeloit" wrote:
[vbcol=seagreen]
> More info - it is a Pull initiated at the subscriber. If I run the same
> application on the Publisher, and make the updates, then replicate, the
> change gets to the subscriber, just not the other way around.
> "SteveInBeloit" wrote:
Wednesday, March 7, 2012
Merge Replication Doesn't Update IDENT_CURRENT() ?
office has a different INDENT_CURRENT value in each branch. Is this
correct?
Basically, I have a table called "Batch" in two database servers (one
for each branch office). Let's call the database servers dbsOne, and
dbsTwo. "Batch" table has an identity field that is not the primary
key and is not the replication ID either. Somehow we find that
IDENT_CURRENT() in dbsOne is different from that's in dbsTwo, like
this:
IDENT_CURRENT("Batch") in dbsOne: 1073
IDENT_CURRENT("Batch") in dbsTwo: 943
When I check the identity values of "Batch" entries that the users have
added in dbsOne, the identity values is closely following
IDENT_CURRENT("Batch") in dbsOne.
Likewise, when I check the identity values of "Batch" entries that the
users have added in dbsTwo, the identity values is closely following
IDENT_CURRENT("Batch") in dbsTwo.
Seem like the merge replication doesn't update IDENT_CURRENT()
accordingly.
Is my understanding correct?
Thanks.
Jay Chan
yes, this is perfectly normal. Basically it means that on one subscriber the
merge agent has run more frequently than on the other.
Hilary Cotter
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
<jaykchan@.hotmail.com> wrote in message
news:1120749290.480181.201600@.g49g2000cwa.googlegr oups.com...
> I have found that a table that is being merge-replicated to each branch
> office has a different INDENT_CURRENT value in each branch. Is this
> correct?
> Basically, I have a table called "Batch" in two database servers (one
> for each branch office). Let's call the database servers dbsOne, and
> dbsTwo. "Batch" table has an identity field that is not the primary
> key and is not the replication ID either. Somehow we find that
> IDENT_CURRENT() in dbsOne is different from that's in dbsTwo, like
> this:
> IDENT_CURRENT("Batch") in dbsOne: 1073
> IDENT_CURRENT("Batch") in dbsTwo: 943
> When I check the identity values of "Batch" entries that the users have
> added in dbsOne, the identity values is closely following
> IDENT_CURRENT("Batch") in dbsOne.
> Likewise, when I check the identity values of "Batch" entries that the
> users have added in dbsTwo, the identity values is closely following
> IDENT_CURRENT("Batch") in dbsTwo.
> Seem like the merge replication doesn't update IDENT_CURRENT()
> accordingly.
> Is my understanding correct?
> Thanks.
> Jay Chan
>
|||Thanks for telling me that this is normal. I will have to keep this in
mind and not using the identity field for synchronizing data between
branch offices and only use it to ID an entry generated within the
branch office. OK.
I don't quite understand what do you mean by "one subscriber the merge
agent has run more frequently than on the other". My database servers
situation is actually like this:
o I have three database servers:
1. dbsOne (the publisher)
2. dbsTwo (The subscriber # 1)
3. dbsThree (The subscriber # 2)
o The INDENT_CURRENT("Batch") value in each database server are:
1. dbsOne: 10734
2. dbsTwo: 9841
3. dbsThree: 9289
o The estimated volume of data added to "Batch" table from
each branch office into their database server are:
1. dbsOne: High
2. dbsTwo: Medium
3. dbsThree: Low
I assume what you mean is that the value in IDENT_CURRENT in each
database server is corresponding to the number of entries that we add
to the table in the database server. This seems to match the numbers
that I get from our database servers. Thanks.
Jay Chan
Hilary Cotter wrote:[vbcol=seagreen]
> yes, this is perfectly normal. Basically it means that on one subscriber the
> merge agent has run more frequently than on the other.
> --
> Hilary Cotter
> 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
> <jaykchan@.hotmail.com> wrote in message
> news:1120749290.480181.201600@.g49g2000cwa.googlegr oups.com...
Saturday, February 25, 2012
merge replication corruption (system triggers and views)
Msg 550, Level 16, State 1, Procedure MSmerge_ins_E3F43EF8B259476099BBB194A2E1708C, Line 42
The attempted insert or update failed because the target view either specifies WITH CHECK OPTION or spans a view that specifies WITH CHECK OPTION and one or more rows resulting from the operation did not qualify under the CHECK OPTION constraint.
The statement has been terminated.
Currently, the only solution I've found is to delete the publication and recreate it. I'm trying to figure out why this happened. It happened on a development server that to my knowledge, hasn't been changed in a week or so outside of changing the server's IP address. Would that cause such an error to occur?
-mikeI found another change.. we added a linked server using sp_addlinkedserver.. Any thoughts?|||Does your merge subset filter clauses or join filter clauses contain views that contain WITH CHECK OPTION, pointing to remote table?|||No filters are set for the publication.|||
ok, then you have to trace your steps to see exactly what changes were made that would cause this, and see if you can back them out one by one.
any idea what the linked server would have to do with regards to the views, triggers, or any of the published tables? are you making changes from a remote machine?
Monday, February 20, 2012
Merge Replication and Multiple Record UPDATE statements
multiple records, usually in the hundreds or thousands.
Is this a problem when using Merge replication? Because there are individual
merge triggers on each table, is it preferable to use a cursor to make global
changes?
Also, when using View Conflicts feature, is it safe to assume that record
listed as the winner has already been replicated to all locations? If so, why
does one have to click on either the Keep Winning Change or the Resolve With
This Data button?
Is there a way to globally accept all winning changes?
The global update will take far longer with merge replication. A cursor
solution might offer better performance.
Regarding the conflict viewer, it is safe to assume that the conflict has
been resolved with the publisher and one subscriber. It might then conflict
with another subscriber, so you can't assume it has been resolved
everywhere.
The keep winning change button and the resolve with this data buttons allow
you to clear the conflict (in other words accept it) or roll it back and let
the subscribers change win.
Hilary Cotter
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
"elpepe" <elpepe@.discussions.microsoft.com> wrote in message
news:D5C598DA-05F0-4F98-A869-DA53D058D628@.microsoft.com...
> We have a database in which global updates must be periodically made to
> multiple records, usually in the hundreds or thousands.
> Is this a problem when using Merge replication? Because there are
> individual
> merge triggers on each table, is it preferable to use a cursor to make
> global
> changes?
> Also, when using View Conflicts feature, is it safe to assume that record
> listed as the winner has already been replicated to all locations? If so,
> why
> does one have to click on either the Keep Winning Change or the Resolve
> With
> This Data button?
> Is there a way to globally accept all winning changes?
|||Thanks -- that's very helpful.
There are hundreds of conflicts that remain. Is there a way to globally
accept the winner so that the conflicts are resolved everywhere?
Also, will you be writing a book on Merge replication anytime soon?
"Hilary Cotter" wrote:
> The global update will take far longer with merge replication. A cursor
> solution might offer better performance.
> Regarding the conflict viewer, it is safe to assume that the conflict has
> been resolved with the publisher and one subscriber. It might then conflict
> with another subscriber, so you can't assume it has been resolved
> everywhere.
> The keep winning change button and the resolve with this data buttons allow
> you to clear the conflict (in other words accept it) or roll it back and let
> the subscribers change win.
> --
> Hilary Cotter
> 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
>
> "elpepe" <elpepe@.discussions.microsoft.com> wrote in message
> news:D5C598DA-05F0-4F98-A869-DA53D058D628@.microsoft.com...
>
>
Merge Replication + Structure Changes
replication approach. It's difficult to update all 40 databases when a
structure change occurs. Structure changes are minor, usually adding
fields.
We are considering moving to SQL Server 2000 in the hope that these
updates will be easier to do. Does SQL Server 2000 support structure
updates accross replicated databases?
Martin"Martin McNally" <mcnally_martin@.hotmail.com> wrote in message
news:3cf569e1.0405031052.574c19e9@.posting.google.c om...
> My company maintains 40 replicated Sybase databases using a merge
> replication approach. It's difficult to update all 40 databases when a
> structure change occurs. Structure changes are minor, usually adding
> fields.
> We are considering moving to SQL Server 2000 in the hope that these
> updates will be easier to do. Does SQL Server 2000 support structure
> updates accross replicated databases?
> Martin
MSSQL supports adding or dropping columns while using any type of
replication. You might want to post this in
microsoft.public.sqlserver.replication, as people there may be able to give
more detail about any common issues or disadvantages.
Simon|||mcnally_martin@.hotmail.com (Martin McNally) wrote in message news:<3cf569e1.0405031052.574c19e9@.posting.google.com>...
> My company maintains 40 replicated Sybase databases using a merge
> replication approach. It's difficult to update all 40 databases when a
> structure change occurs. Structure changes are minor, usually adding
> fields.
> We are considering moving to SQL Server 2000 in the hope that these
> updates will be easier to do. Does SQL Server 2000 support structure
> updates accross replicated databases?
> Martin
hello martin!!
Try dbMaestro. It's a product that allows comparison, migration and
archiving of database schema and data in Sql Server 2000. by migration
you can updates structures of databases and data.
You can find it here:
http://www.extreme.co.il