How to add new article into running merge replication and what are the steps need to take please tell me.
View Complete Post
I have a publication on SQL Server 2008 Standard Edition using merge replication. When I attempt to generate the initial snapshot, the snapshot agent appears to hang on the step "Setting up the publication for filtered articles." I
get a long (over 4 hour) series of messages: "The process is running and is waiting for a response from the server." I know something is happening server-side, as SQL Server and the snapshot agent use a lot of memory and max out one core's
This has me confused as the publication is not doing any filtering.
Even more confusing: I backed up the database and restored it onto my development-test system. I created the snapshot there, and it took under 10 minutes every time.
Any suggestions for investigating and resolving this?
Currently running merge replication on SQL Server 2008 10.0.1600 and having issues with adding and modifying triggers on published articles. I've searched through the MSDN site and googled it but have not found any definitive information on correct
We have a replicated table that had 1 trigger on it when it was added to the publication. That trigger was replicated. We have since added a 2nd trigger to the table and it is not being replicated to our other server. I've checked the Article
Properties and Copy User Triggers is set to TRUE. The only difference is the new trigger has NOT FOR REPLICATION in it, but I thought that would only keep it from being executed if a row is effected by the MERGE process.
We have rerun the snapshot and are syncing continuosly and the trigger does not replicate. Do I have to drop the tablefrom the publication and then re-add it? Am I missing something?
We are planning to implement Merge Replication between SQL Server 2008 "Not R2 Version" (Publisher) and SQL Server 2005 (Subscriber). Will this setup work, or there are some limitations ?
I have hit a road block while trying to setup merge replication using SQL Server 2008 R2 Express. I have the publication working fine. from a test computer with standard SQL Server 2008 R2 installed, I can synchronize with a pull subscription.
The Database server is windows 2008. We have an active directory with Windows 2003 DCs.
I have configured the laptops to synchronize while connected to the LAN. I was tying to avoid the additional complexity if Internet Synchronization
I was uable to get the pull subscription to work with SQL Server 2008 Express, so I set up an identical laptop with the standard version of SQL Server and was able to synchronize both from the Management Studio and from the front-end application.
The problem seems to be with the disabled SQL Server agent in the Express version
The agent job is never created from the SQL Studio or from the published code I used to create the subscription and agent job.
The error I get when I try to sync in code is:
merge_job_login update with value DOMAIN\MyRepAgent failed
the specified job does not exist.
MyRepAgent has all the rights I could give that login. I set that account up and used it as the login account of the SQL Agent Service on both laptops.
Is there a step by step article or white paper anywhere about setting up pull subscriptions u
I have 2 clustered instances running on SQL Server 2008 SE-64 patch level 10.0.2531.0. These is one DB on these 2 instances (compatibility_level=80)under merge replication. now I need to change one trigger to add "NOT FOR REPLICATION". One publisher site
all is ok but on subscriber site it causes Error 102 Severity 15 State 1 Incorrect Syntax near 'dbo'.
After tracing the error in profiler, I captured the incorrect syntax as below:
exec('ALTER TRIGGER [dbo].[trgBusinessEntityAllocationUpdate] on [dbo].[BusinessEntityAllocation]
NOT FOR REPLICATION
SET NOCOUNT ON
obviously, there is an duplicated part of object name. but the script was generated by replication engine. How could it happened? can anyone help?
We have a customer with three publications, one distributor/publisher and on subscriber using merge replication.
looking at the history of the job replication agents checkup, every entry shows a message of:
Executed as user: NT AUTHORITY\SYSTEM. The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections
to the Subscriber, Publisher, and Distributor are still active. [SQLSTATE 01000] (Message 20554). The step succeeded.
Throughout the day this error still appears as this job runs every 10 minutes but replication works fine. The issue is at some point throughout the night the replication stops with that same message. Sometimes it stops at 6:00:00am, sometimes at 6:40:00am,
others at 6:50:00am. All we have to do to fix it is go into the replication monitor and stop synchronizing and then start synchronizing and replication will run all day until it stops next morning - again.
What is causing that error message? I have checked the other logs and there is nothing running at those times. in addition, no one has logged into the server that early (they don't start arriving until 7:15 or later).
What can i do to correct the issue so the message stops happening.
Hi, i have a publisher with 3 publications with below SQL
Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86) Nov 24 2008 13:01:59 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
I want to add a subscriber to the server with below SQL
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.0 <X64> (Build 6002: Service Pack 2) (VM)
Now when i am trying to add subscritpion to the 2008 R2 server on the publication server, i am getting below message
TITLE: New Subscription Wizard
For merge publications, the version of the Subscriber must not exceed the version of the Publisher.
Is merge replication not possible between the 2?? Please advice. I beliwve Microsoft's new releases should support its older versions...
I've searched far and wide, and so far have not been able to find any reference to this issue.
There is a merge replication setup on a SQL 2008 server, setup to replicate to SQL 2008 Express edition. We have similar setups in SQL 2005 AND SQL 2008 without issues. The setup is that the current merge replication snapshot file location is
\\<ServerName>\Repldata\UNC\<SERVER_PUBLICATION>\20101229112828 which represents the file location of the latest snapshot which was just generated due to an obsolete snapshot.
The issue comes in when attempting to replicate against the server. The replication says that the schema script could not be propogated to the subscriber. Under normal circumstances I would say it's due to security issues with being able to read to the above
folder, however this is not the case. The additional error that comes up is stating that it could not read the file along with an OS error 3 (The system cannot find the path specified).
What is unique about this, is that the subscriber is trying to download the snapshot from an old and now non-existent snapshot folder. Here is an copy of the error, noting the file location of "20091121130613" which no longer exists and is from an old snapshot.