oh, what a gaff!

That's a proper newbie mistake; running round in circles assuming you've missed something. A very salutary lesson for any other newcomers to IT training...

big...

mmm. In the Conflict Viewer, the Conflict Loser displays the following error message:

A row update at 'SERVER1.AdventureWorks' could not be propagated to 'SERVER1.SubTesting'. This failure can be caused by a...

Oh, it appears that if I now 'View Syncronization Status' and press 'Start' then the changes in both tables are replicated, producing the intended 'conflict'. So the "Msg 208,...

The owner of the Distribution DB is 'sa'...

Ok,

So again I execute:

USE AdventureWorks

UPDATE Production.Product

SET Name=Name+'Updated at Publisher'

WHERE ProductID=1

USE SubTesting

UPDATE Production.Product

SET Name=Name+'Updated at Subscriber'

WHERE ProductID=1

and receive the following message:

"(1 row(s) affected)

(1 row(s) affected)

Msg 208, Level 16, State 1, Procedure...

Thanks Brandie,

Mercifully this is just a test database, and the setup is based on the 'Configuring Conflict Resolution for Merge Replication' chapter of the MCTS 70-431 textbook. The purpose...

I think assumed that a two-way data-flow would be the default state for a 'merge' replication set-up. The text book talked about a two-way data flow being the main...

ooops, I now know what I did wrong...and it was a bit stupid! :blush:

I ran through the practices a number of times in order to address various issues that...

Hi Joie

In order to address that question, I need to delve into the scripts produced by SSMS at various stages of the practice sequence. Please bear in mind that...

I just came across this error and found that, in my case, it was caused when restoring the backup from one instance onto another, without altering the 'save database as'...

Ah, thanks! That explains a lot.

At the moment I am focusing on learning SQL and Excel VBA but thought that familiarity with Server 2005 would be useful. It...