Hi Aaron, thanks for those two links. pretty good info in those two. 🙂

It could take a different plan based on whether it is parametazid or not. I read that in Grant Fritcheys blog.

The overlapping auto stats is the one that makes...

Check if you have overlapping auto stats. That could cause this.

I forgot the fact that you are using SQL 2008. I was thinking it was SQL 2005. Anyways, I gave you a bad advice last time. When your distributor version...

The Publisher is SQL 2000, right? Are you doing a PULL or a PUSH subscription? That could make a big difference when using two different versions of SQL Server for...

Dag namit, this has gone to 4 pages and still not resolved. Not good. The only other thing I can think of that could happen is the Snapshot schema is...

When you were looking at the profiler, what was the user that was being used to connect and execute?

This is a Microsoft product... 🙂 So expect the worst. You can try this in two ways.

1. Remove this PK violation command from replication

2. Remove the row from the...

Now run the profiler and find out the exact cause of the problm. I have seen case where it sends two commands for the same SP.

Also run the sp_browsereplcmds...

Check in your Subscriber database if the stored proc sp_MSins_dboDocumentNotes exists in your replicated database and the service used in the distributor and the distributor_admin have DBO rights on the...

On the distributor Database, ALPHA\dtwservice, what is the Default database set for it? Make sure that the default DB is Master. Since it is a sysadmin in all the instances,...

In your SQL Server Log and Event viewer, that is all the errors details you get? Or are there more errors? Also we need to find out what is failing....

Add the distributor admin to the sysadmin group. On both the publisher and the distributor. When you add an article, the Distributor_admin adds a row in the syspublication table. For...

Log on to your publisher and then try connecting to your distributor using SSMS. I have a bad feeling that your connections from the publisher to distributor is somehow getting...

Can you run this command on the distributor?

Use Master

go

Select @@Servername

Check if it gives the right name.