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

More Related Resource Links

I am looking to see if we have any way to set on the subcsriber to avoid accidental deletes on subscriber tables to avoid the 20598 error(where the publisher is trying to replicate a record not existing(rather deleted in accident) at the subscriber end).
This is for transactional replication

I have configured transactional replication on 7 databases from an sql server 2005 to another sql server 2005.

One of them has 487 tables and when I check "Replication Monitor" it shows that everything ok, but database above , that shows the message "Performance Critical".

My question is : The tables have been replicated or not ? How can I check this ? It´s not possible check table per table. Anyone suggests any other way to check if tables and their data have been replicated.

I set up a transactional replication, publisher 2005 SP2 to a subscriber SQL 2008r2. The database is about 90 GB. When I want to create a Snapshot, the snapshot agent is running to 96% and then give a error. I have set up some logging, here is the tail of
it:

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?

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!

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.

Hi all,
I've SQL Server 2005 and a transactional replication scenario with one puplisher and 11 subscribers. Sometimes one of the subscriptions fails and a manual operation is required. Is there a way to get an e-mail notification whenever the replica fails or stucks
or simply degrade its performances?

We recently upgraded from SQL 2000 to SQL 2005 SP3 and I am noticing something that I think is a bug with replication from a publication that has an article in it with row filters. It seems to be that if the row filter has columns that are bit datatype and that column is updated on the publisher to cause the row filter to exclude it, it is not removed from the subscriber. If you update a column that is part of the row filter that is not a bit datatype it works as expected. I can reproduce this in a test environment with a small base table. In production this is resulting in an occasional 20598 error "The row was not found at the Subscriber when applying the replicated command". Is anyone aware of a hotfix that addresses this? I can think of a few work arounds but the table is rather large and I really would like to avoid having to pull replication, re-snap or changing datatypes on the base table etc. Any suggestions are greatly appreciated. Thanks!

I am trying to figure out why I can't access the DB that I've replicated. Two tables have a key with a red x that makes it so I can't publish them for replication. In addition, how do I replicate all the user roles and permissions with the database
that is being replicated? I am using SQL Server 2000.
More info: I can't access the replicated DB through the client software. It is accessible through SQL Management Console. I had to manually export all users and roles and then run the query to get them into the replicated database.
Is there a more thorough way to replicate a database? How can I make an exact copy on a different server so all information is intact?

1.I need to Replicate a db without replicating its constraints, only the tables. What is the best way to achieve this?
2.Need the Subcription(replicated db) to have the collation of the server being replicated to. Please explain how the options need to be configured. Thanks

Hi guys,
I am after some advice as to my replication setup and what I can do with it. I have only basic knowledge of replication but have had transactional replication setup for a while now which replicates a few of the main databases tables and it is working
fine. However we want to improve performance of our subscriber database, so I would like to use row filters for this.
Imagine the setup of a database table for Questionnaires which has a Void bit field in it, and a table for Answers. On the subscriber I want only non-void Questionnaires and their answers. So I set the row filter for the Questionnaire table to be "WHERE
Void = 0", I think this works. However, I don't think it works when I am working on the Answers table, my row filter would be "WHERE QuestionnaireID IN (SELECT QuestionnaireID FROM Questionnaires WHERE Void = 0).
This works fine for the initial snapshot but not for following transactions. For example, if I made a Questionnaire not void then I'd expect that to make its way to the subscriber along with its answers. Or if I voided a Questionnaire I'd expect that Questionnaire
and set of answers to be removed from the subscriber database.
I have read that this type of filter that uses a subquery only works with merge replication, if my understanding is correct?
So my question here is, can you validate my findings, is

Im running transactional replication sql 2008 and have a couple table names with the same name but different schemas. I want to make sure in the replication that the filegroups stay with the subscriber. Is this possible?
I.E
Table AAA.Customer on file group A
Table BBB.Customer on file group B
Is there a way to keep these filegroups without rebuilding the index after it has been moved? I noticed there was an option in the replicaiton options to keep file group but it doesn not seem to help. Can you let me know how. THANKS>

I am newbie to SQL 2005 and doing my first project (I am an exchange/AD Consultant). I am trying to do a transactional replcation across a VPN link. I have humdreds and hundreds of tables to be replicated. I have around 100 tables which are
without any primary key. I am using
http://blogs.techrepublic.com.com/howdoi/?p=123 for configuration.

I am able to replicate the tables which are with Primary keys, can't replicate any tables which are without primary keys. I am sure there must be a work around or some solution for the tables without primary keys.

I am not able to replicate few tables of a database using snapshot replication.Both publisher and subscriber are in different network and domain.Although I am able to replicate 950 tables but facing problem in some 30 tables.I am using push replication and
I can telnet 1433 port from A server to B server but vice versa not happening.When I am replicating few records of that few tables it is replicating properly but not able to replicate complete table. I tried Verbose history too but I didn't get complete error.

I have a Database which contains about 15 tables that 10 of them should be replicated to another database which its schema is "EXACTLY" same with the publisher. The 5 tables that are not planed to publish, have no rows all over the time (indeed the subscriber
DB is just a template DB that should be synchronized becuase of some reasons)...

At snapshot definition I just set each table to Truncate All rows at initialization level. But the problem was that it drop all indeces automatically and FK Constrains which causes the different schema in subscriber DB. So I dcided to set to Copy ALL of
related objects (indeces,FKs,cluster indeces,triggers ,...) at initialization level. But the problem is with 5 tables that are not published when all their relations with the other 10 tables will be droped at initialization level....Beside of all these problems
I get FK constraint error at initialization time...

Also I should mentioned that my DB version is 2000 SP4.

Did I miss or misunderstood something? or should I choos another solution? or some problem in SQL 2000 and should migrate to 2005 or 2008?