| Author |
Topic |
|
nejc
Starting Member
17 Posts |
 Posted - 2005-08-19 : 09:29:48
|
| helloAfter a bit of problems at start, i managed to create a merge and a snapshot replication. I have a few questions now and am hoping someone here will know to answer them.1. Is it possible to make a merge replication work 1 way only ? From publisher to subscriber. For example: I am on a publisher PC, and i change the data, which is later replicated to all of the subscribers. The subscribers should be able to update and modify their own tables, but only locally. When i would change my version of the table, it would only add the data into their tables, without deleting what they have added seperately.2. Do the names of the tables always have to be the same for merge/snapshot replication to work, or is there a way to use different names, and just assign which table replicates into which one.3. I used a test replication on my own pc (locally). It was a merge type. I had 1 database and created a few tables in it and entered some data. Then i copied the whole database, so the new one had same named tables then the first on. Now i create a new table in my first database. How do i make it replicate without creating a table in the second database manually ?Thanks for the answers. I appreciate it. |
|
|
nejc
Starting Member
17 Posts |
Posted - 2005-08-22 : 02:41:03
|
| I figured out question 3. It apperantley creates it automatically when a new snapshot is transffered.I still have problems blocking subscribers from updating the data. This is what i currently need the most, so if anyone knows that or can link me to the solution, i would greatly appreciate it.Thanks. |
 |
|
|
nejc
Starting Member
17 Posts |
Posted - 2005-08-22 : 03:40:23
|
| ok i found out i have to put exchangetype in the merge agent job step. I couldnt find exact directions anywhere. I tried just making a new step in the job list, and typing exchangetype 2 in it, i also tried exchange_type 2, but it does not work. |
|
|
|
nejc
Starting Member
17 Posts |
Posted - 2005-08-22 : 04:10:39
|
| i found a good site where the issue is explained, but unfortunetly it does not solve my problem. I would use a transactional replication, but it is not available to me, as i am using an sql server 2000 "personal edition". Do you think that might be a reason that exchangetype doesnt work either ?The site i mentioned is:[url]http://www.replicationanswers.com/MergeChangesArticle1.asp[/url] |
|
|
|
mblythe
Starting Member
16 Posts |
Posted - 2005-08-22 : 18:37:44
|
| I'm sorry I don't have a copy of 2000 in front of me, so I don't have the exact steps... You do not need to add a job step; you need to add the parameter to the existing job step that runs the agent (you could also add it to an agent profile). The jobs UI should include a step that executes the merge agent command line, similar to:-Publisher <PublisherName> -Subscriber <SubscriberName>, etc. To add the parameter, you need to edit this job step. Add the following to the end:-ExchangeType 2Michael Blythe Technical WriterSQL Server Replication - Microsoft --------------------------------------------------------------------------- This posting is provided "AS IS" with no warranties, and confers no rights. |
|
|
|
nejc
Starting Member
17 Posts |
Posted - 2005-08-23 : 03:38:55
|
oh yeah, i got tired of posting yesterday, but i figured it out. I was doing it right, i only had to restart the agent.... Thanks for the replay anyway :) |
|
|
|
spart
Starting Member
5 Posts |
Posted - 2007-12-04 : 08:06:22
|
| I am having the same problem too.I am trying to use Merge Replication in SQL2005 to replicate only one way to the subscriber but any changes that occur in the subscriber are being replicated back to the publisher ideas how to handle this? |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2007-12-04 : 08:32:15
|
quote:
Originally posted by spart
I am having the same problem too.I am trying to use Merge Replication in SQL2005 to replicate only one way to the subscriber but any changes that occur in the subscriber are being replicated back to the publisher ideas how to handle this?
Why are you using merge replication?==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
|
merge replication: one-way only