.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Fauzul Azmi
Asad Ali
Post New Web Links

Replication falling behind over a WAN

Posted By:      Posted Date: August 28, 2010    Points: 0   Category :Sql Server
I’ve been stuck on a replication problem for a few weeks now and am getting rather desperate.   We’ve been using replication of our production databases successfully for a couple years now to a local server for reporting purposes, but now we’re attempting to also use it over a WAN for disaster recovery in a remote location.  Our current setup is as follows:   5 production databases on 5 separate servers 5 distributors on 5 separate servers 1 subscriber for all replicated databases   Now we’re trying to add 5 more subscribers for disaster recovery, using the original publications and distributors.  All databases involved are SQL 2005 and we’re using transactional replication with push subscriptions.  So far I’ve been able to get replication working for 3 of the 5 databases, but as soon as the snapshot is delivered for a fourth, replication starts falling behind for that database only, and it never catches up.  Transactions are replicating successfully, but just not nearly fast enough.   I’ve tried replicating each of the two remaining databases separately as the fourth instance, and I’ve tried stopping replication to everything except for these databases, and I get the same results.  The remaining two databases do happen to be the biggest (2-4 GB) and the busiest (up to 400,000 dist

View Complete Post

More Related Resource Links

transactional replication falling behind. millions of transactions in sp_brosereplcmds

Hi, Hi All, we have transactional replication set up with all the agents running at source database. The synchronization status is stuck at "delivering replication transactions". The replication latency in replication monitor says excellent. when I check sp_browsereplcmds. it ever ends. It has over more than millions of rows of output. We were having trouble with this replciation recently because at the source db. they run a large batch. So we decided to schedule snapshot agent to run exactly after that batch but the snapshot doesn't seem to helping out with the latency. what should be done to resolve the issue. Please help. thanks.

merge replication system tables fragmentation issue

I have Merge replication going on in my environment. The problem is that system tables like MSmerge_content, MS merge _tombstone and MSmerge_genhistory are getting fragmented. We are rebuilding indexes time to time daily. But we want some good fix. Just send some good idea guys?

peer to peer replication, drop and add article of same name

We have peer-to-peer replication set up on our system (2005 EE). I would like to change the metadata of one of the tables (many of the tables actually, but right now I'm just trying to test out the process with just one table). As this is a high-availability system, I would like to stop the replication, make the changes on one node, verify that the changes are working, make the same changes on the other node, then re-enable replication. The ddl changes to the table are extensive enough that I have to clear them before executing. So I will handle re-populating the tables in a later step. Right now I'm just testing the process of stopping, doing ddl, then restarting. I am trying to implement this using scripts so as to minimize my clicking (and thus potential for mistakes) when doing it for real. I find that if I do the following process using the SSMS interface it goes smoothly with no errors (note that each step is conducted on both nodes unless specified): stop sync agents manually remove article: tblName1 with 'publications properties window' close 'publications properties window' make ddl changes to tblName1 (change column names, add columns etc. to a particular table) manually add article: tblName1 with 'publications properties window' re-enable agents But if I try the following, I get 'Peer-To-Peer topologies require identical articles in publications at all n

Transactional replication: Updates to one of my columns (sometimes) does not get replicated from the

hi, This is my scenario: I have a varchar(max) column on a table that is replicated to other servers. I have a stored procedure that does and update to this column and other columns on the table. This is done inside a transaction that also includes other updates. When I call the stored procedure, this one varchar(max) column's value is not replicated. When I just run the single update statement on its own, the value is replicated. Anyone know something about this? Thanks!    

Steps by Step document for configuration Merge Replication in 2005

Hi , Can anyone provide link to configure Merge Replication in 2005 with print screen.Also let me know the difference between Transcation level and Merge Replication. regards Vijay  

transactional replication and sp_MSupd tables

Hi thre, My target server keeps running sp_MSupd sp for different values in profiler and synch status shows "delivering replication commands" I keep waiting but this never ends. and ultimately we run a snapshot and it can't be applied. So recreate the whole replication again. It runs fine for a while but again, the sp_MSupd sp starts running on the target server and the replication goes down again. I don't know how to fix this. any advices?   Regards

Real-time data replication

Are there any ways to replicate sql server production database to a standby database? I notice that there is a feature called 'continuous replication', does it do in real-time? what is the time-lag? Are there any potential data loss (i.e., production transaction committed but production db corrupted before the transaction is sent to standby)? Is the standby database available for read access during the replication?

SQL Server 2005 Merge Replication

We did the following: We setup a database with all of standard tables, views, etc. We then put in place merge replication for a few of the tables within this database, including a tables called "Areas". We can execute SQL statements to insert rows into this table fine. We then applied an update script for this database to change a few tables by adding fields and changing indexes, etc.  We didn't change the "Areas" table though. After the update to the database structure, we get an error when trying to insert into this "Areas" table. The error message was the following: The insert failed. It conflicted with an identity range check constraint in database 'AETest', replicated table 'dbo.Areas', column 'AREPrimaryId'. If the identity column is automatically managed by replication, update the range as follows: for the Publisher, execute sp_adjustpublisheridentityrange; for the Subscriber, run the Distribution Agent or the Merge Agent.  The statement has been terminated.   What would cause such a problem and how do we resolve it?  The structure of the "Areas" table before and after the update is the following: USE   [AETest] GO /****** Object: Table [dbo].[Areas] Script Date: 08/24/2010 17:42:36 ******/ SET   ANSI_NULLS ON GO SET   QUOTED_IDENTIFIER ON GO SET   ANSI_PADDING ON

Merge Replication: How to give read access on snapshot share to a sql account

Hello All, I want to give read access to an sql account(not windows account). Can it be given or not. Someone please tell. Thanks saandii777

SQL 2008 geography type replication

Hi, I am attempting to get merge replication going between two SQL 2008 servers.  So far, everything has gone off without a hitch with one exception.  We use spatial data on a daily basis in my organization, so we implemented the geography data type.  This data type seems to be causing all of our replication issues.  I can easily create publications and subscriptions for each article in the entire database except the geography field. The error is as follows: "The Merge Agent failed because the schema of the article at the Publisher does not match the schema of the article at the Subscriber. This can occur when there are pending DDL changes waiting to be applied at the Subscriber. Restart the Merge Agent to apply the DDL changes and synchronize the subscription." The real kicker is that the schemas are exactly the same.  If I set the publication to drop and recreate the subscription article, then to convert the geography data type, it works without issue, but then we run into issues with our publication database not matching exactly with our subscription database, which could cause many potential problems with our web front end.   Is there a known issue with replicating the geography data type?  Any help is very much appreciated! - Chad  

One way replication

I want to achieve replication of a SQL Server 2008 database over a one way connection, meaning that I can transfer files from the source database machine to the target database machine but not the other way around. Besides file transfer there is no means of communication between the servers. The source database will have to be online continuously. The target database too, but it will be used for reading only. How could I get this done? I have tried log shipping. It works but the restore taking place at the target database requires an exclusive lock on the database. But I do not want to abort any sessions on the target database.   Any ideas? Thanks in advance, Frans

Sql Server 2008 R2 Replication

Dears, I am make a testing environment before implementing it into real world. I have 3 servers SQL 2008 R2, i configured 1 Publisher, 2 Subcribers with a merged replication. Everything is Ok. However, i have an ID field on Publisher which is autonumber(Start by 1, increment by 1). When I try to add new record on publisher, it takes it 1 by 1 i.e. 1-2-3.... But i try to add it on subscriber it starts with 20,000 i.e. 20001, 20002. I think this is logical for SQL, but can i define this number on the subscriber? So it will start on 200,000 for example? Another question, In LAN i can connect the subscriber to the publisher, it will connect to it directly, since it is broadcast. But in WAN environment how can the subscriber detects the publisher??? Your reply is highly appreciated, Thanks in advance,

replication from oracle to SQL

Command attempted: Error messages: ·   Invalid distribution command, state 2: transaction 0x0x0000000000000000081e00000000 command 3{offset : 430 token offset: 429 state: 50) }. (Source: MSSQL_REPL, Error number: MSSQL_REPL21001) The above shown message is the one message which i am getting while replicating from oracle to SQL. In development it is working but not in Prod. What is the solution of above error for failed subscription?

SQL 2008 Upgrade Replication failure

we upgraded to Sql 2008 standard edition last night from 2000 and our replication is now failing, cannot delete it or enter new ones.   I found one article saying the following stored procedures need to be run to upgrade the replcation:   exec sp_vupgrade_replication  exec sp_vupgrade_repl_metadata   however the first one throws and error and the second one seems not to exists.  does anyone have any insight into this. or how to delete the replications?   the error from the stored proc sp_vupgrade_replication  is :   Upgrading subscription settings and system objects in database [SoxAuditSystem]. Attempting to copy article resolvers from SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\Replication\ArticleResolver Msg 25026, Level 16, State 1, Procedure sp_registercustomresolver, Line 82 The proc sp_registercustomresolver cannot proceed because it is not run in the context of the distribution database, or the distribution database is not properly upgraded.  

Replication and auto Identity Increment

We want to have two SQL server working on the same data at the same time (SQL Server 2008). I've been told that the auto ID's will stop working (the identity option). I'm not sure how true this is or what is the best replication to use for this.   Thanks

Replication stored procedures not being passed parameters- default appears instead

Hi I am setting up transactional replication from Oracle to SQL Server, it is working fine for 9 tables, but for one it fails on updating and deleting with a message like this: Procedure or function 'spu_VGSM_SUBMISSION_CONTACT' expects parameter '@pkc1', which was not supplied. This is correct, in that the sp should be being passed this parameter, but when I do a trace it will show something like: exec "spd_VGSM_SUBMISSION_CONTACT" '12-3456-10','BLOGGS','S', '2010-07-01 12:43:43', 'M123456' default In other words, the old primary key values which should be being passed in are being replaced with "default". I am using the CALL syntax for the update sp. If anyone can suggest why this is I would be very grateful. This is the publication: exec sp_addpublication @publication = N'_Submission_Contact', @description = N'Transactional publication from Oracle Publisher.', @sync_method = N'concurrent_c', @retention = 0, @allow_push = N'true', @allow_pull = N'true', @allow_anonymous = N'false', @enabled_for_internet = N'false', @snapshot_in_defaultfolder = N'true', @compress_snapshot = N'false', @ftp_port = 21, @ftp_login = N'anonymous', @allow_subscription_copy = N'false', @add_to_active_directory = N'false', @repl_freq = N'continuous', @status = N'active', @independent_agent = N'true', @immediate_sync = N'
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend