microsoft.public.sqlserver.replication | Forum profile

  Merge is great for certain scenarios but I wouldn't personally use merge as a DR solution. Log shipping can incur little downtime if you ship the logs every few minutes and it includes everything in the database. In my last position they were using replication as a dr solution and when I used SQLCompare I noticed loads of differences between the publisher and subscriber, especially in the indexes and users. Also, merge...

  "Paul Ibison" wrote: > There is a note in BOL about this "If the source table for an article is > already published in another publication, the value of > subscriber_upload_options must be the same for both articles." > I suppose another option would be to use transactional replication for the > read-only version. > Cheers, > Paul Ibison,...

  I'm having a problem with a transactional publication failing to add records from a updatable subscriber on 2000 SP4. When the Queue Reader Agent runs I get the 'could not find stored proceedure ins.sp_MSsync_ins_articlename' error. The one article I can find on the subject states that the problem is the value of queue_id in the MSsubscription_agents table on the subscriber, which should be 'mssqlqueuev2'....

  When running a merge from a C# application I get the following message if the user is not an administrator. It does not throw an exception, another process seems to be displaying a dialog box. "Invalid handle attempting to load message from resource DLL" I found another post dated Jun 27 2006 but it went unanswered. Vista Business Edition SQL Express 2005 SP1 ..Net 2.0  

  Hi, I have question regarding to add new articles. Right now I start snapshot agent every time in order to replicate new table and relavant data into subscription after I add new articles. I monitor replication and found it seems like it re-transfer all articles into subscriber again, which I think will cause huge time to synchronize if I have larger database in the future. How can I just transfer only new acticle and relavant data...

   

  Hello, we have the same Problem after et recently upgrade too. Did you find a solution ? url: http://www.ureader.com/msg/11563657.aspx  

  Paul thanks for the reply, I got some info in the meantime. The existing setup is logshipping. The new proposed setup woudl be two active SQL servers connected through merge replicaiton to porvide higher up time. One of the concern is what if one of the servers is taken down for maintenance, would it effect merge replicaiton. My reply was that the merge replicaiton will catch up once the server comes backup. Please share your...