View Complete Post
Currently running merge replication on SQL Server 2008 10.0.1600 and I have a few questions around the correct procedures for adding and modifying triggers on published articles. I've searched through the MSDN site and googled this but have
not found any definitive information on correct procecdures.
1) When a new trigger is added to a published table do we just have to rerun the snapshot and then re-syncy the subscribers? Just adding them does not seem to replicate them to subscribers.
2) When an existing trigger is modified should ALTER TRIGGER be used or should the trigger be dropped and then re-added?
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?
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?
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 am Planning to Add new SQl Server 2008R2 Instance to SQL Server 2000 SP4 in Windows 2003 SP2 OS and As of now all the storage in SAN drive
Here problem is my company is going to move SAN drive to iSCSI and they given me iSCSI drives to Install SQL Server 2008R2 and they ask me Create Quorum drive on iSCSI.
1. Is it possible to create one more Quorum Drive or I need to move excisting Quorum to new Drive
I have below Groups in SAN Drive and I want Move those groups to iSCSI Drives what is best way ..to do this with minimum Down time.
Cluster Ip Adress
MSDTC IP Adress
SQL IP IpAdress(SQLCLUSTER)
SQL Network Name(SQLCLUSTER)
SQL Server Name
SQL Server Agent
SQL Server Fulltext
Thanks in Advance
Hi All, I have a windows service running on Windows 2008 server, when I set the service to log on as Local System account, it works fine and does the ssl certificate authentication.
Where as when I change the service to log on to a different account it fails with the authentication error.
Could some one please help me here.
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 have implemented Merge replication in sql server 2008
after fre days i add new articles to the merge replication next day i found one error (see below)
The merge process was unable to access row metadata at the 'Subscriber'. When troubleshooting,
restart the synchronization with verbose history logging and specify an output file to write to,
or use SQL Profiler to determine the source of the failure. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200996)
Get help: http://help/MSSQL_REPL-2147200996
TCP Provider: An existing connection was forcibly closed by the remote host. (Source: MSSQLServer, Error number: 10054)
Get help: http://help/10054
Communication link failure (Source: MSSQLServer, Error number: 10054)
Get help: http://help/10054
The process was successfully stopped. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199481)
Get help: http://help/MSSQL_REPL-2147199481
How to solve this isseus, please help me in this,
I have create a subscription (pull, merge replication) on SQL Server 2008 R2 Express Edition to a publication on SQL Server 2008 R2 Enterprise Edition. I have seen that the subscription has been enabled for Windows Sychronization Manager as I can see in
its property dialog. However, I cannot see it in the Sync Center of Windows 7 on the Subscriber.
Does Sync Center support in this scenario? From
another thread, it seems we need to use Windows Task Manager. If so, how can I set it up?
Thanks in advance.
Hi, we are using SQL Server 2008 with Pull Merge Replication.
We are experiencing some strange behavior with triggers on replicated Articles.
We have the following trigger:
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.