Google is your friend:

http://www.databasejournal.com/features/mssql/article.php/1438201/Setting-Up-Transactional-Replication-A-Step-by-step-Guide.htm

This was definitely a "new" distribution database setup.

eric.winters (4/30/2010)

---

Hello and thanks for your time.

I've been successfully snapshot replicating tables from Oracle 11g to SQL2005 for some time. Recently the need came up and we are trying...

Recursion of stored procedures is always a bad Idea.

You should use a CTE (or any other method you feel comfortable with) to determine which IDs you need deleted and then...

josebrwn (4/29/2010)

---

I think you are right!

The puzzling bit is that replication agents continue happily along, as though nothing were the matter. You have to look in the application event...

🙂 Looks like the OP is not clarifying either ... oh well ...

My only advice in that case would be to remove replication the "hard way" and start from scratch.

EXEC sp_removedbreplication 'dbname'

Ronzo (4/29/2010)

---

You stated " enabled this option by typeing this command -MaxCmdsInTran 10000 at log reader and distribution agent job parameters after -continuous".

There is no MaxCmdsInTran parameter documented for the...

Your primary probably issued a *delete* and your row "was already not present" at the subscriber!

Well I assumed you had "transactional replication" maybe you have "merge"; can you check sysmergearticles ?

Looks like you have created indexed views for all your tables!!!!

To starters get rid of all "Create Unique CLUSTERED INDEX ...." for <tablename>_<view>

If you run that query frequently you will be much better off using an indexed view.

Forget it ... we know the answer is that it is probably in GB .... or who knows if it was actually...

Yup front end is the way to go for these kind of things.

Did you look in dbo.sysarticles ?

1. Once you figure out which subscriber has it (if any) you do this:

EXEC dbo.sp_dropsubscription @publication = N' publication name',

...