Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » replication   (RSS)

How to reapply SQL 2000 SP4 to update all the 13 scripts

Due to any issue, you may want to rerun SQL 2000 SP4 upgrade. SQL 2000 Service Packs are cumulative. But when you re-run SP4 it only updates 7 Scripts those are new with SP4. This could be useful when SQL Server is already on SP3 and due to some reason Read More...
Posted Saturday, January 31, 2009 3:09 AM by sanjayap | 1 Comments

Issue with constraints on the subscriber in Merge Replication

We have configured Merge replication in SQL Server and we have the replicated constraint's name on the subscriber is different from the constraints on the publisher. It is possible that we will have the constraints on the subscriber even after they have Read More...
Posted Monday, January 05, 2009 8:55 PM by sanjayap | 1 Comments

Log Reader Agent Fails with the Error “The Log Reader Agent failed to construct a replicated command from log sequence number (LSN)”

Recently we encountered a case where in the Log Reader Agent fails to run and the following error is reported in the Replication Monitor Error messages: The process could not execute 'sp_replcmds' on 'TXDAL01410'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011) Read More...
Posted Tuesday, December 30, 2008 2:24 PM by sanjayap | 4 Comments

Did you know... Merge Replication Fails with Error 'Unable to synchronize the row because the row because the row was updated by a different process outside of replication.'

Recently we have encountered a case where Merge Agent was failing to apply a transaction at the subscriber with the following error Error Message ============== The change for the row with article nickname 2336003 (test), rowguidcol {D46DF7AF-38C5-4B74-B07D-CF46A4E3B7EB} Read More...
Posted Wednesday, December 17, 2008 12:45 PM by sanjayap | 1 Comments

Log Reader Agent Fails when the Sql server instance is failed over to Node 2

We have observed a number of case where we use sql server replication on a clustered instance of sql server and when we try to failover from Node 1 to Node 2 the Log Reader agent may fail to start with the following error Error messages: The process could Read More...
Posted Monday, November 24, 2008 12:09 PM by sanjayap | 2 Comments
Filed under: ,

How to setup a SQL Server Replication between three servers in a typical scenario..

Three Servers (Top, middle and Bottom) Data will flow from Top to the Bottom Server. Top to Middle Server (one way Replication) and Middle to Last Server (two ways Replication). ================================================= ----> Top Server----> Read More...
Posted Friday, October 31, 2008 2:14 PM by sanjayap | 1 Comments

Did you know… When we rename a domain group in Active Directory, we can have some issues related to the login in SQL Server

Sometime back I got to work on an interesting issue related to the login on the SQL Server replication. The Active Directory group we used to grant access to a snapshot publication does not show up in the Publication access list anymore when viewing the Read More...
Posted Sunday, October 26, 2008 9:33 PM by sanjayap | 1 Comments

Step by Step Procedure to Implement SQL Server Transactional Replication with Oracle as Publisher

/*** Note: Kindly follow the Instruction in each step ***/ /*** If you are using SQL Server 2008 Management Studio, Ctrl-Shift-M might not work. In that case go to “Query” menu and click on “Specify Values for Template Parameters” ***/ 1) Logon to ORACLE Read More...
Posted Thursday, October 16, 2008 6:59 PM by sanjayap | 2 Comments

Did you know… The applications like Infopath may fail to submit data into table in SQL Server if the table is included in Merge replication

You are able to submit the data in the table using the application like InfoPath 2007 but when you go ahead and add the table in the Merge Replication Publication, the insert into the table using the InfoPath form starts to fail. This issue occurs when Read More...
Posted Sunday, October 05, 2008 3:54 PM by sanjayap | 1 Comments

The subscription fails to Sync with the Publisher and marked inactive even though the settings have been configured to “never expire”

We get the below error message when distribution agent tries to sync, Error: 14151, Severity: 18, State: 1. The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated. CAUSE: ====== Read More...
Posted Saturday, October 04, 2008 10:02 PM by sanjayap | 1 Comments
 
Page view tracker